oreka-devel Mailing List for oreka

Hi All,

The first 0.5 windows installer was missing a file
(orkaudio-0.5-1-win32-installer.zip). This prevented OrkAudio to function
properly.
I have corrected it and an updated installer is available for download
(orkaudio-0.5-2-win32-installer.zip).

Cheers
Henri

-----Original Message-----
From: ore...@li...
[mailto:ore...@li...] On Behalf Of Henri Herscher
Sent: 16 February 2006 21:44
To: ore...@li...
Subject: [Oreka-devel] Oreka 0.5 is out

Hi all,

Oreka 0.5 has been released. The changelog is as follows:

* Fixed a critical bug that could cause Orkaudio to crash given a certain
sequence of RTP packets
* Fixed a SIP detection issue on Siemens platform (Siemens Optipoint 400)

Cheers
Henri

Hi all,

Oreka 0.5 has been released. The changelog is as follows:

* Fixed a critical bug that could cause Orkaudio to crash given a certain
sequence of RTP packets
* Fixed a SIP detection issue on Siemens platform (Siemens Optipoint 400)

Cheers
Henri

Hi all,

Oreka 0.4 has been released. The changelog is as follows:

* Oreka can now monitor multiple Network devices in parallel
* Oreka can now replay tcpdump (pcap) network trace files
* Improved RTP detection (Before: some RTP streams could go undetected)
* Improved Cisco Skinny signalling management (Before: Sessions could break
up spuriously and single session could be seen as two separate sessions)
* Improved SIP detection (Before: SIP messages on some platforms went
undetected)
* Improved SIP signalling management (Before: Sessions could break up
spuriously)
* Oreka can now store in "pcmwav" format, ie, pcm stored in a wav file
without compression
* Sample rate can now be different than 8KHz across Oreka
* Sample rate now tunable in SoundDevice plugin
* Codecs can now be plugins

Cheers
Henri

Hi again Martin,

You can easily change your web server port number by tweaking the database:

update service set fileServeTcpPort=8080 where 1;

Orkaudio itself does not have a port number, you actually need to set it to
output audio files in your Tomcat ROOT directory so that they can be served
by Tomcat. Just do this in your config.xml file:

<AudioOutputPath>/path/to/tomcat/webapps/ROOT</AudioOutputPath>

Cheers
Henri

-----Original Message-----
From: ore...@li...
[mailto:ore...@li...] On Behalf Of Martin Gysi
Sent: 06 February 2006 05:40
To: ore...@li...
Subject: [Oreka-devel] Logging: Tomcat on port !=8080

Figured out why reporting wasn't working: Tomcat defaults to port 8180 on a 
standard FreeBSD installation. Hence, another input for version 0.4: tunable

port number using config.xml. :-)

Cheers,
Martin


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Oreka-devel mailing list
Ore...@li...
https://lists.sourceforge.net/lists/listinfo/oreka-devel

Hi Martin,

Yes, thank you, the RTP port range is now >1024 in CVS head.

StdString.h has been updated so that you don't need -fpermissive with recent
versions of gcc (CVS head also).

Cheers
Henri

-----Original Message-----
From: ore...@li...
[mailto:ore...@li...] On Behalf Of Martin Gysi
Sent: 06 February 2006 05:17
To: ore...@li...
Subject: [Oreka-devel] Detection of SIP

Hi Henri

I figured out why my SIP phone wasn't detected: It's using UDP source port 
1025, and you're filtering out everything below 5000 in VoIp.cpp. Worked
fine 
once I fixed it, you may want to change this for 0.4.

btw, I also had to use -fpermissive using gcc 3.4.4 to get it to compile.

one more thing: Logging to orktrack doesn't work yet. I enabled Reporting 
using <EnableReporting>true</EnableReporting>, and checked all file 
permissions, but no entries on the webpage. orktrack and orkweb seem to be 
up, but tomcat manager says that orktrack has 0 running sessions. What else 
should I check?

  /orktrack  orktrack  true  0    Start   Stop   Reload   Undeploy   
  /orkweb  orkweb  true  1    Start   Stop   Reload   Undeploy 


Cheers,
Martin


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Oreka-devel mailing list
Ore...@li...
https://lists.sourceforge.net/lists/listinfo/oreka-devel

Figured out why reporting wasn't working: Tomcat defaults to port 8180 on a 
standard FreeBSD installation. Hence, another input for version 0.4: tunable 
port number using config.xml. :-)

Cheers,
Martin

Hi Henri

I figured out why my SIP phone wasn't detected: It's using UDP source port 
1025, and you're filtering out everything below 5000 in VoIp.cpp. Worked fine 
once I fixed it, you may want to change this for 0.4.

btw, I also had to use -fpermissive using gcc 3.4.4 to get it to compile.

one more thing: Logging to orktrack doesn't work yet. I enabled Reporting 
using <EnableReporting>true</EnableReporting>, and checked all file 
permissions, but no entries on the webpage. orktrack and orkweb seem to be 
up, but tomcat manager says that orktrack has 0 running sessions. What else 
should I check?

  /orktrack  orktrack  true  0    Start   Stop   Reload   Undeploy   
  /orkweb  orkweb  true  1    Start   Stop   Reload   Undeploy 


Cheers,
Martin

Hi Henri,
	Thanks for your quick reply.  I will probably just wait for oreka 0.4 
to be released, however it turns out I'm not using gcc4.  I'm currently 
on gcc-3.4.5, but I have got it building using the hardened specs and 
pic enabled, which often cause me difficulties when compiling packages, 
perhaps it's this?  It's definitely using -O2 and I think the only other 
unusual flag (beside the hardened flags) is -fomit-frame-pointer. 
Anyway, I look forward to trying out the new version when it's 
released...  5:)
	Mike  5:)

Hi Mike,

This is a problem I've seen with StdString.h when compiling with gcc4. You
have several options.

* Compile with the following gcc switch: -fpermissive (will produce tons of
warnings)
* Use gcc3
* Use cvs head instead 0.3 where StdString.h has been upgraded (or else wait
for oreka 0.4 that I should release probably this week).

Cheers
Henri

-----Original Message-----
From: ore...@li...
[mailto:ore...@li...] On Behalf Of Mike Auty
Sent: 05 February 2006 12:23
To: ore...@li...
Subject: [Oreka-devel] Compilation problems under linux...

Hi,
	I'm trying to create a gentoo ebuild so that I can test out oreka 
easily, however I'm having a few build problems.  I've managed to get 
autoconf and automake etc to create a configure script which runs and 
seems all successful.  The problem however arrives once I start to 
compile orkbasecxx using make.  I get the folloing error back, and I'm 
not sure what to do to fix it.  Any ideas, comments or suggestions for 
things I can try would be greatly appreciated.  If there's any further 
information I can provide to help diagnose the problem, just ask and 
I'll be happy to provide it.  Thanks,
	Mike  5:)

make  all-recursive
make[1]: Entering directory `/home/mike/tmp/oreka-0.3/orkbasecxx'
Making all in messages
make[2]: Entering directory `/home/mike/tmp/oreka-0.3/orkbasecxx/messages'
if /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I. -I.. -I..   -D_REENTRANT -g -O2 -MT AsyncMessage.lo -MD -MP -MF 
".deps/AsyncMessage.Tpo" -c -o AsyncMessage.lo AsyncMessage.cpp; \
then mv -f ".deps/AsyncMessage.Tpo" ".deps/AsyncMessage.Plo"; else rm -f 
".deps/AsyncMessage.Tpo"; exit 1; fi
mkdir .libs
  g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -D_REENTRANT -g -O2 -MT 
AsyncMessage.lo -MD -MP -MF .deps/AsyncMessage.Tpo -c AsyncMessage.cpp 
-fPIC -DPIC -o .libs/AsyncMessage.o
In file included from ../OrkBase.h:26,
                  from Message.h:22,
                  from AsyncMessage.h:18,
                  from AsyncMessage.cpp:14:
../StdString.h: In member function `CStdStr<CT>& CStdStr<CT>::ToUpper()':
../StdString.h:1959: error: there are no arguments to `empty' that 
depend on a template parameter, so a declaration of `empty' must be 
available
../StdString.h:1959: error: (if you use `-fpermissive', G++ will accept 
your code, but allowing the use of an undeclared name is deprecated)
../StdString.h: In member function `CStdStr<CT>& CStdStr<CT>::ToLower()':
../StdString.h:1978: error: there are no arguments to `empty' that 
depend on a template parameter, so a declaration of `empty' must be 
available
../StdString.h: In member function `CT* CStdStr<CT>::GetBuf(int)':
../StdString.h:2001: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h: In member function `CStdStr<CT> CStdStr<CT>::Mid(int) 
const':
../StdString.h:2908: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h: In member function `CStdStr<CT> CStdStr<CT>::Mid(int, 
int) const':
../StdString.h:2921: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h:2922: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h:2924: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h:2928: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
make[2]: *** [AsyncMessage.lo] Error 1
make[2]: Leaving directory `/home/mike/tmp/oreka-0.3/orkbasecxx/messages'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mike/tmp/oreka-0.3/orkbasecxx'
make: *** [all] Error 2


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Oreka-devel mailing list
Ore...@li...
https://lists.sourceforge.net/lists/listinfo/oreka-devel

Hi,
	I'm trying to create a gentoo ebuild so that I can test out oreka 
easily, however I'm having a few build problems.  I've managed to get 
autoconf and automake etc to create a configure script which runs and 
seems all successful.  The problem however arrives once I start to 
compile orkbasecxx using make.  I get the folloing error back, and I'm 
not sure what to do to fix it.  Any ideas, comments or suggestions for 
things I can try would be greatly appreciated.  If there's any further 
information I can provide to help diagnose the problem, just ask and 
I'll be happy to provide it.  Thanks,
	Mike  5:)

make  all-recursive
make[1]: Entering directory `/home/mike/tmp/oreka-0.3/orkbasecxx'
Making all in messages
make[2]: Entering directory `/home/mike/tmp/oreka-0.3/orkbasecxx/messages'
if /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I. -I.. -I..   -D_REENTRANT -g -O2 -MT AsyncMessage.lo -MD -MP -MF 
".deps/AsyncMessage.Tpo" -c -o AsyncMessage.lo AsyncMessage.cpp; \
then mv -f ".deps/AsyncMessage.Tpo" ".deps/AsyncMessage.Plo"; else rm -f 
".deps/AsyncMessage.Tpo"; exit 1; fi
mkdir .libs
  g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -D_REENTRANT -g -O2 -MT 
AsyncMessage.lo -MD -MP -MF .deps/AsyncMessage.Tpo -c AsyncMessage.cpp 
-fPIC -DPIC -o .libs/AsyncMessage.o
In file included from ../OrkBase.h:26,
                  from Message.h:22,
                  from AsyncMessage.h:18,
                  from AsyncMessage.cpp:14:
../StdString.h: In member function `CStdStr<CT>& CStdStr<CT>::ToUpper()':
../StdString.h:1959: error: there are no arguments to `empty' that 
depend on a template parameter, so a declaration of `empty' must be 
available
../StdString.h:1959: error: (if you use `-fpermissive', G++ will accept 
your code, but allowing the use of an undeclared name is deprecated)
../StdString.h: In member function `CStdStr<CT>& CStdStr<CT>::ToLower()':
../StdString.h:1978: error: there are no arguments to `empty' that 
depend on a template parameter, so a declaration of `empty' must be 
available
../StdString.h: In member function `CT* CStdStr<CT>::GetBuf(int)':
../StdString.h:2001: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h: In member function `CStdStr<CT> CStdStr<CT>::Mid(int) 
const':
../StdString.h:2908: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h: In member function `CStdStr<CT> CStdStr<CT>::Mid(int, 
int) const':
../StdString.h:2921: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h:2922: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h:2924: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
../StdString.h:2928: error: there are no arguments to `size' that depend 
on a template parameter, so a declaration of `size' must be available
make[2]: *** [AsyncMessage.lo] Error 1
make[2]: Leaving directory `/home/mike/tmp/oreka-0.3/orkbasecxx/messages'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mike/tmp/oreka-0.3/orkbasecxx'
make: *** [all] Error 2

Hi Martin,

Glad to see oreka compiles fine on FreeBSD, are you interested in sound
device capturing or VoIP capturing ? Have you already tested orkaudio
capture ?

Please notify this list if you have a port ready so that I can update the
news on the oreka.org website.

Cheers
Henri

-----Original Message-----
From: Martin Gysi [mailto:ma...@gy...] 
Sent: 03 February 2006 08:25
To: Undisclosed.Recipients :
Cc: Henri Herscher
Subject: Sucess: Compilation on FreeBSD

Hi Henri

I finally managed to get orkaudio working on FreeBSD, and am now working on 
the Java portion. I'll write a port this weekend :-)

Thanks for your help, the log4cxx hint put me on the right track.

Cheers,
Martin

Hi Henri

It seems that my last mail didn't go out yesterday. So here again:

I compiled log4cxx successfully using the following command sequence:

libtoolize13 --force --automake
aclocal15
autoheader253
autoconf253
automake15 --add-missing

./configure; gmake

It looks like my system is set up correctly to compile libtool based programs. 

Cheers,
Martin


Am Donnerstag 02 Februar 2006 17:27 schrieb Henri Herscher:
> Hi Martin,
>
> You could try to configure and compile any of the prerequisite libraries
> for oreka: log4cxx, ace or xerces (without installing). If this works, what
> I can do is to do a "make dist" and send you the output of that so that you
> don't need to exercise your autotool chain, you'll be able to run
> ./configure straight away.
>
> Henri
>
> -----Original Message-----
> From: ore...@li...
> [mailto:ore...@li...] On Behalf Of Martin Gysi
> Sent: 02 February 2006 11:19
> To: ore...@li...
> Subject: Re: [Oreka-devel] Compilation on FreeBSD
>
> Hi Henri
>
>
> I haven't compiled a libtool-based program "by hand" yet, as on FreeBSD
> this
>
> is usually automated by the ports system. The ports system compiles
> everything from scratch, my guess is that it should also work fine for a
> libtool based program. Do you know another program with which I could make
> a
>
> test?
>
>
>
> This sequence has so far worked with the least amount of errors and
> warnings:
>
> mgysi@frodo ~/oreka-0.3/orkbasecxx $ libtoolize15 --force
> You should add the contents of `/usr/local/share/aclocal/libtool15.m4' to
> `aclocal.m4'.
> mgysi@frodo ~/oreka-0.3/orkbasecxx $ aclocal15
> mgysi@frodo ~/oreka-0.3/orkbasecxx $ autoheader213
> mgysi@frodo ~/oreka-0.3/orkbasecxx $ automake14
> mgysi@frodo ~/oreka-0.3/orkbasecxx $ autoconf213
>
> however, configure fails with a libtool error again
>
> ./ltconfig: Can't open ./ltconfig: No such file or directory
> configure: error: libtool configure failed
>
>  Adding AC_PROG_LIBTOOL didn't help...
>
> Martin
>
> > Hi Martin,
> >
> >
> >
> > I'm by no mean an autotools guru. I'm just wondering if you can actually
> > configure and build another libtool based program, just to check that
> > your versions of autoconf/automake/libtool play well together ? Have you
> > tried adding AC_PROG_LIBTOOL in your configure.in ?
> >
> >
> >
> > Henri
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Oreka-devel mailing list
> Ore...@li...
> https://lists.sourceforge.net/lists/listinfo/oreka-devel
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Oreka-devel mailing list
> Ore...@li...
> https://lists.sourceforge.net/lists/listinfo/oreka-devel

Hi Martin,

You could try to configure and compile any of the prerequisite libraries for
oreka: log4cxx, ace or xerces (without installing). If this works, what I
can do is to do a "make dist" and send you the output of that so that you
don't need to exercise your autotool chain, you'll be able to run
./configure straight away.

Henri

-----Original Message-----
From: ore...@li...
[mailto:ore...@li...] On Behalf Of Martin Gysi
Sent: 02 February 2006 11:19
To: ore...@li...
Subject: Re: [Oreka-devel] Compilation on FreeBSD

Hi Henri


I haven't compiled a libtool-based program "by hand" yet, as on FreeBSD this

is usually automated by the ports system. The ports system compiles 
everything from scratch, my guess is that it should also work fine for a 
libtool based program. Do you know another program with which I could make a

test?



This sequence has so far worked with the least amount of errors and
warnings:

mgysi@frodo ~/oreka-0.3/orkbasecxx $ libtoolize15 --force
You should add the contents of `/usr/local/share/aclocal/libtool15.m4' to 
`aclocal.m4'.
mgysi@frodo ~/oreka-0.3/orkbasecxx $ aclocal15
mgysi@frodo ~/oreka-0.3/orkbasecxx $ autoheader213
mgysi@frodo ~/oreka-0.3/orkbasecxx $ automake14
mgysi@frodo ~/oreka-0.3/orkbasecxx $ autoconf213

however, configure fails with a libtool error again

./ltconfig: Can't open ./ltconfig: No such file or directory
configure: error: libtool configure failed

 Adding AC_PROG_LIBTOOL didn't help...

Martin


> Hi Martin,
>
>
>
> I'm by no mean an autotools guru. I'm just wondering if you can actually
> configure and build another libtool based program, just to check that your
> versions of autoconf/automake/libtool play well together ? Have you tried
> adding AC_PROG_LIBTOOL in your configure.in ?
>
>
>
> Henri


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Oreka-devel mailing list
Ore...@li...
https://lists.sourceforge.net/lists/listinfo/oreka-devel

Hi Henri


I haven't compiled a libtool-based program "by hand" yet, as on FreeBSD this 
is usually automated by the ports system. The ports system compiles 
everything from scratch, my guess is that it should also work fine for a 
libtool based program. Do you know another program with which I could make a 
test?



This sequence has so far worked with the least amount of errors and warnings:

mgysi@frodo ~/oreka-0.3/orkbasecxx $ libtoolize15 --force
You should add the contents of `/usr/local/share/aclocal/libtool15.m4' to 
`aclocal.m4'.
mgysi@frodo ~/oreka-0.3/orkbasecxx $ aclocal15
mgysi@frodo ~/oreka-0.3/orkbasecxx $ autoheader213
mgysi@frodo ~/oreka-0.3/orkbasecxx $ automake14
mgysi@frodo ~/oreka-0.3/orkbasecxx $ autoconf213

however, configure fails with a libtool error again

./ltconfig: Can't open ./ltconfig: No such file or directory
configure: error: libtool configure failed

 Adding AC_PROG_LIBTOOL didn't help...

Martin


> Hi Martin,
>
>
>
> I'm by no mean an autotools guru. I'm just wondering if you can actually
> configure and build another libtool based program, just to check that your
> versions of autoconf/automake/libtool play well together ? Have you tried
> adding AC_PROG_LIBTOOL in your configure.in ?
>
>
>
> Henri

Hi Martin,

 

I'm by no mean an autotools guru. I'm just wondering if you can actually
configure and build another libtool based program, just to check that your
versions of autoconf/automake/libtool play well together ? Have you tried
adding AC_PROG_LIBTOOL in your configure.in ?

 

Henri

 

  _____  

From: Martin Gysi [mailto:ma...@gy...] 
Sent: 02 February 2006 10:51
To: Henri Herscher
Subject: Re: [Oreka-devel] Compilation on FreeBSD

 

Hi Henri

Here's the output for orkbasecxx, with the latest installed version of each
tool:

mgysi@frodo ~/oreka-0.3/orkbasecxx $ libtoolize15 --force

You should add the contents of `/usr/local/share/aclocal/libtool15.m4' to
`aclocal.m4'.

then

mgysi@frodo ~/oreka-0.3/orkbasecxx $ aclocal19

/usr/X11R6/share/aclocal/imlib.m4:9: warning: underquoted definition of
AM_PATH_IMLIB

run info '(automake)Extending aclocal'

or see http://sources.redhat.com/automake/automake.html#Extending-aclocal

/usr/X11R6/share/aclocal/imlib.m4:167: warning: underquoted definition of
AM_PATH_GDK_IMLIB

/usr/X11R6/share/aclocal/gtk.m4:7: warning: underquoted definition of
AM_PATH_GTK

aclocal:configure.in:10: warning: macro `AM_PROG_LIBTOOL' not found in
library

then

mgysi@frodo ~/oreka-0.3/orkbasecxx $ autoheader259

--> no error here

mgysi@frodo ~/oreka-0.3/orkbasecxx $ automake19

messages/Makefile.am:2: Libtool library used but `LIBTOOL' is undefined

messages/Makefile.am:2:

messages/Makefile.am:2: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'

messages/Makefile.am:2: to `configure.in' and run `aclocal' and `autoconf'
again.

messages/Makefile.am: required file `./depcomp' not found

serializers/Makefile.am:2: Libtool library used but `LIBTOOL' is undefined

serializers/Makefile.am:2:

serializers/Makefile.am:2: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'

serializers/Makefile.am:2: to `configure.in' and run `aclocal' and
`autoconf' again.

Makefile.am:6: Libtool library used but `LIBTOOL' is undefined

Makefile.am:6:

Makefile.am:6: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'

Makefile.am:6: to `configure.in' and run `aclocal' and `autoconf' again.

then

mgysi@frodo ~/oreka-0.3/orkbasecxx $ autoconf259

configure.in:10: error: possibly undefined macro: AM_PROG_LIBTOOL

If this token and others are legitimate, please use m4_pattern_allow.

See the Autoconf documentation.

configure finally fails with this output:

mgysi@frodo ~/oreka-0.3/orkbasecxx $ ./configure

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for gawk... no

checking for mawk... no

checking for nawk... nawk

checking whether make sets $(MAKE)... yes

checking for g++... g++

checking for C++ compiler default output file name... a.out

checking whether the C++ compiler works... yes

checking whether we are cross compiling... no

checking for suffix of executables...

checking for suffix of object files... o

checking whether we are using the GNU C++ compiler... yes

checking whether g++ accepts -g... yes

checking for style of include used by make... GNU

checking dependency style of g++... none

./configure: line 2436: AM_PROG_LIBTOOL: command not found

configure: creating ./config.status

config.status: creating Makefile

config.status: error: cannot find input file: Makefile.in

Depending on the versions of the tools I use I get further and the
Makefile.in gets created. However, configure will always complain about
libtool, either it's not made at all, or it produces output that can't be
processed further.

Any helpful ideas?

Martin

Am Donnerstag 02 Februar 2006 16:10 schrieben Sie:

> Hi Martin,

> 

> I have successfully built orkbasecxx/orkaudio using automake 1.4/autoconf

> 2.59 on a Ubuntu Hoary system as well as automake 1.9.6/autoconf 2.59 on a

> SuSE10 system.

> 

> What kind of errors are you seeing ?

> 

> Cheers

> Henri

> 

> -----Original Message-----

> From: ore...@li...

> [mailto:ore...@li...] On Behalf Of Martin Gysi

> Sent: 02 February 2006 09:57

> To: ore...@li...

> Subject: [Oreka-devel] Compilation on FreeBSD

> 

> Hi

> 

> I'm trying to make oreka work on a FreeBSD machine. The problem is that

> there

> are many different versions available of the auto* - toolchain
(libtoolize,

> aclocal, autoheader, automake, autoconf). All of them behave differently,

> and

> I haven't found a combination that creates a working configure script, let

> alone a succesful compilation.

> 

> Could you tell me the version numbers of the tools that you use to compile

> orkbasecxx?

> 

> Thanks,

> Martin

> 

> 

> -------------------------------------------------------

> This SF.net email is sponsored by: Splunk Inc. Do you grep through log

> files for problems? Stop! Download the new AJAX search engine that makes

> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!

> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

> _______________________________________________

> Oreka-devel mailing list

> Ore...@li...

> https://lists.sourceforge.net/lists/listinfo/oreka-devel

Hi Martin,

I have successfully built orkbasecxx/orkaudio using automake 1.4/autoconf
2.59 on a Ubuntu Hoary system as well as automake 1.9.6/autoconf 2.59 on a
SuSE10 system.

What kind of errors are you seeing ?

Cheers
Henri

-----Original Message-----
From: ore...@li...
[mailto:ore...@li...] On Behalf Of Martin Gysi
Sent: 02 February 2006 09:57
To: ore...@li...
Subject: [Oreka-devel] Compilation on FreeBSD

Hi

I'm trying to make oreka work on a FreeBSD machine. The problem is that
there 
are many different versions available of the auto* - toolchain (libtoolize, 
aclocal, autoheader, automake, autoconf). All of them behave differently,
and 
I haven't found a combination that creates a working configure script, let 
alone a succesful compilation.

Could you tell me the version numbers of the tools that you use to compile 
orkbasecxx?

Thanks,
Martin


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Oreka-devel mailing list
Ore...@li...
https://lists.sourceforge.net/lists/listinfo/oreka-devel

Hi

I'm trying to make oreka work on a FreeBSD machine. The problem is that there 
are many different versions available of the auto* - toolchain (libtoolize, 
aclocal, autoheader, automake, autoconf). All of them behave differently, and 
I haven't found a combination that creates a working configure script, let 
alone a succesful compilation.

Could you tell me the version numbers of the tools that you use to compile 
orkbasecxx?

Thanks,
Martin