libtool-patches
[Top][All Lists]
Advanced

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

Re: libtoolize bugs in HEAD


From: Ralf Wildenhues
Subject: Re: libtoolize bugs in HEAD
Date: Thu, 31 Mar 2005 16:41:19 +0200
User-agent: Mutt/1.4.1i

Hi Gary,

* Gary V. Vaughan wrote on Tue, Mar 29, 2005 at 08:56:07PM CEST:
> Ralf Wildenhues wrote:
> > No time for looking now, but libtoolize HEAD contains
> > 
> > # Massage a value for pkgvltdl_files from the value used in Makefile.am
*snip*
> I can't reproduce this:

Hehe.  :)

> ] cvs -d `cat libtool--devo--1.0/CVS/Root` co -d HEAD libtool
> ] cd HEAD
> ] ./bootstrap
> ] mkdir +build && cd +build
> ] ../configure
> ] make
> ] fgrep COPYING.LIB libtoolize
    for my_filename in make[3]: Entering directory `/tmp/libtool/build/libltdl' 
COPYING.LIB README Makefile.am Makefile.in configure.ac configure ltdl.c ltdl.h 
lt_error.c libltdl/lt_error.h libltdl/lt__private.h libltdl/lt__strl.h 
libltdl/lt_system.h lt__alloc.c libltdl/lt__alloc.h libltdl/lt__glibc.h 
libltdl/lt__dirent.h slist.c libltdl/slist.h lt_dlloader.c 
libltdl/lt_dlloader.h loaders/preopen.c lt__dirent.c libltdl/lt__dirent.h 
lt__strl.c libltdl/lt__strl.h argz_.h argz.c loaders/Makefile.am 
loaders/Makefile.in loaders/dld_link.c loaders/dlopen.c loaders/dyld.c 
loaders/load_add_on.c loaders/loadlibrary.c loaders/shl_load.c make[3]: Leaving 
directory `/tmp/libtool/build/libltdl'; do

> ] cd ..
> ] rm -rf +build
> ] ./configure
> ] make
> ] fgrep COPYING.LIB libtoolize
    for my_filename in make[3]: Entering directory `/tmp/libtool/libltdl' 
COPYING.LIB README Makefile.am Makefile.in configure.ac configure ltdl.c ltdl.h 
lt_error.c libltdl/lt_error.h libltdl/lt__private.h libltdl/lt__strl.h 
libltdl/lt_system.h lt__alloc.c libltdl/lt__alloc.h libltdl/lt__glibc.h 
libltdl/lt__dirent.h slist.c libltdl/slist.h lt_dlloader.c 
libltdl/lt_dlloader.h loaders/preopen.c lt__dirent.c libltdl/lt__dirent.h 
lt__strl.c libltdl/lt__strl.h argz_.h argz.c loaders/Makefile.am 
loaders/Makefile.in loaders/dld_link.c loaders/dlopen.c loaders/dyld.c 
loaders/load_add_on.c loaders/loadlibrary.c loaders/shl_load.c make[3]: Leaving 
directory `/tmp/libtool/libltdl'; do

> Perhaps you have out of date Makefile.in or mismatched bootstrap script?

Obviously not.  Did you use GNU make and bash?

> > and thus breaks horribly.  That fixed, an installed version moans about
> > 
> > /tmp/install/libtool-2.1/bin/libtoolize --copy --force --install -I m4
> 
> This is telling libtoolize to find the master sources in ./m4 rather than
> $prefix/share/libtool-2.1a.  The macros will be installed to whichever
> directory is specified as an argument of option -I in ACLOCAL_AMFLAGS in
> Makefile.am, or else in AC_CONFIG_MACRO_DIR if ACLOCAL_AMFLAGS is not defined.

Now don't you think choosing `-I' as the option name is a really really
bad idea?  Talk about consistent option naming.  Think stupid user error.

> > /tmp/install/libtool-2.1/bin/libtoolize: line 644: cd: m4/libltdl: No such 
> > file or directory
> 
> libtoolize is warning that the new master source directory doesn't seem to
> contain the libltdl dir.  This might mean that your tmp/install libtoolize
> script has pkgvdatadir et. al. pointing at a non-existent directory.

OK, that is consistent with your statement above.

> > libtoolize: copying file `./config.guess'
> > libtoolize: copying file `./config.sub'
> 
> Although it is copying files from somewhere... can you investigate this 
> please?

Later.

> > libtoolize: warning: no serial number in 
> > `/tmp/install/libtool-2.1/share/libtool-2.1a/install-sh', not copying.
> 
> Hmmm... seems like the version timestamp variable in install-sh has a
> different name to the one I tested with.  I'll post a patch presently.
> 
> Do you want me to make any changes to gary--1.0--patch-11 before committing
> to HEAD btw?

Let's see that in another mail.  I don't have much time ATM.

> > libtoolize: copying file `./ltmain.sh'
> > 
> > of which at least the second one looks quite fishy.
> 
> Good catch.

Thanks.

Cheers,
Ralf




reply via email to

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