RE: [Oreka-devel] Compilation on FreeBSD

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