Re: Upgrading libltdl does not remove old macros

[Gary V. Vaughan]

Hi Roumen,

On 16 Apr 2008, at 16:00, Roumen Petrov wrote:
> Gary V. Vaughan wrote:
> > Hi Andreas,
> > On 15 Apr 2008, at 12:21, Andreas Schwab wrote:
> > > In a project that uses AC_LIBLTDL_CONVENIENCE libtool 1.5 used to  
> > > put
> > > the libtool macros for the libltdl subdir in libltdl/ 
> > > acinclude.m4.  When
> > > running libtoolize 2.2 on such a source directory the libltdl  
> > > directory
> > > is not properly upgraded: libltdl/acinclude.m4 remaines intact, and
> > > although the correct (2.2) libtool macros are propery put in  
> > > libltdl/m4,
> > > they are not found because libltdl/acinclude.m4 takes precedence.
> > Thanks for all the bug reports.
> > Unfortunately, many users of legacy libtool would maintain their  
> > own hand
> > rolled macros in acinclude.m4, so we can't safely throw chunks of  
> > it away
> > with sed :-(
> > I think the best we can offer is to try to notice old libtool  
> > macros in
> > common places, and remind the user to remove them, maybe even  
> > suggesting
> > that a simple 'rm -f' will do the trick as long as they don't have  
> > hand
> > maintained macros in the same file.
> > Cheers,
> >    Gary
>
>
> But file libltdl/acinclude.m4 is not maintained by project. It is  
> installed by old libtool versions (pre 2.x). May be new libtool  
> (2.2+) has to remove it?
>
> If the project contain own acinclude.m4 files with libtool outside  
> installed by libtoolize for ltld the libtool cannotn't touch them.


Exactly.

But there is no way to be sure whether acinclude.m4 contains nothing  
more than
old versions of libtool macros. Therefore it is not safe to delete the  
file even
if libtoolize does see its old macros in there.

Cheers,
        Gary
--
  ())_.              Email me: address@hidden
  ( '/           Read my blog: http://blog.azazil.net
  / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_

PGP.sig
Description: This is a digitally signed message part