[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with invocation of libtoolize?

From: Dan Nicholson
Subject: Re: Problem with invocation of libtoolize?
Date: Tue, 3 Nov 2009 06:03:04 -0800

On Tue, Nov 3, 2009 at 12:13 AM, Christian Egli <address@hidden> wrote:
> Hi all
> I recently migrated liblouis[1] to use gnulib. Everything works
> marvelously for me. I can run autoreconf, configure and make and make
> distcheck cleanly (I use automake 1.10.2, autoconf 2.63 and libtool
> 2.2.6). However some of the co-developers are having problems compiling
> the package with older versions of the tool chain. One error is
> essentially as follows:
> [snip]
> make[3]: Entering directory `/home/lrs/tmp/liblouis-gnulib/gnulib'
> /bin/sh ../libtool --tag=CC   --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H 
> -I. -I../liblouis     -g -O2 -MT progname.lo -MD -MP -MF .deps/progname.Tpo 
> -c -o progname.lo progname.c
> ../libtool: line 833: X--tag=CC: command not found
> ../libtool: line 866: libtool: ignoring unknown tag : command not found
> ../libtool: line 833: X--mode=compile: command not found
> [snip]
> The dev uses Fedora 10 with libtool-1.5.26, autoconf 2.63 and automake
> 1.11. When googling for this problem it appears that some people have
> had this same problem before and that it might be to do with libtoolize
> not being invoked properly by and ultimately autoreconf.
> Indeed if I compare the output of below with the one I'm
> getting, it appears that libtoolize is not invoked with --install. Our
>[2] script essentially just invokes autoreconf with the
> options --force --install --verbose. Is this a problem of an old
> autoreconf? I'm a bit stumped on how to solve this problem. I'd rather
> not force all developers to upgrade to libtool 2.x. Below is a extensive
> log of the output of, configure and make check.

Yeah, the important thing is that autoreconf/libtoolize be invoked
with the --install option. Then when libtoolize is run again it will
update it's support files (i.e., If you don't use
autoreconf --install, aclocal.m4 will be updated anyway with the local
libtool macros, but libtoolize will just do nothing since it would
otherwise "install" files into your source tree.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]