[Top][All Lists]

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

Re: Solving our bootstrap woes

From: Scott James Remnant
Subject: Re: Solving our bootstrap woes
Date: Thu, 15 Jan 2004 15:22:35 +0000

On Thu, 2004-01-15 at 08:33, Gary V.Vaughan wrote:

> Are you sure that aclocal sorts m4 input alphabetically?  I wouldn't be 
> surprised if it just pulls the files from disk in directory order 
> (equivalent to mtime I think).  Or maybe they get m4_included in 
> topographic order...
Yeah, 1.7 uses "sort readdir" and 1.8 uses "reverse sort grep readdir",
either way the effect is enough, lt~obsolete.m4 gets included after the
contents of ltsugar.m4 and libtool.m4.

It's not *that* much of a problem, anyway.  If it gets included before
libtool.m4, the later file just overrides the definitions with the real

> Either way, it only really affects libtool's own bootstrap, since we 
> now remove old libtool.m4s from $prefix/share/aclocal.

> On Thursday, January 15, 2004, at 12:16  am, Scott James Remnant wrote:
> > This isn't a patch, it's just a new file to drop in the distribution as
> > m4/lt~obsolete.m4.  Ok, it needs adding to EXTRA_DIST as well, but
> > that's it.
> Provided we bootstrap with automake 1.8 or newer it will get added 
> automatically (by virtue of being m4_included).
Yeah, worth sticking in though as we can still bootstrap with 1.7

> I think we also don't need add it to pkgmacro_DATA, since it is just 
> noise to libtool users, especially because it might wreak havoc if some 
> future (or old!) version of aclocal manages to slurp it in before 
> libtool.m4.
Correct, it's just for us and doesn't need to be installed.  It probably
shouldn't wreak havoc, but then there's no reason to risk it and confuse
users with it.

> > I think the comment I've put in it explains how it works pretty well,
> > basically instead of whatever you've got in
> > /usr/share/aclocal/libtool.m4 turning up in your aclocal.m4, you get
> > this instead; which is harmless because the filename is asciibetically
> > after anything else in m4/ so the m4_ifdef just expand to [].
> Please add a comment near pkgmacro_DATA in to remind us not 
> to install it too.

Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

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