bug-libtool
[Top][All Lists]
Advanced

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

Re: config.status (or something) writes out a crippled libtool script


From: Gary V. Vaughan
Subject: Re: config.status (or something) writes out a crippled libtool script
Date: Wed, 24 Aug 2005 16:10:22 +0100

On 24 Aug 2005, at 15:32, Ralf Wildenhues wrote:
* Peter Ekberg wrote on Wed, Aug 24, 2005 at 03:40:42PM CEST:
10. make

[ triggers ltmain.m4sh -> ltmain.sh recreation ]

/bin/sh: autom4te: command not found

Gary (or someone else), can you check that I did it correctly?
I always get confused with this stamp-vcl thingy.

stamp-vcl goes out of date after changes from cvs up (i.e the version
in the ChangeLog has changed), so it is a cheap way of saying you
want to force something to rebuild whenever changes have been imported
into the tree.  I added it originally because I wanted version.m4 to
be updated, but loads of stuff has a long chain of dependencies that
lead back to version.m4, so we can make those things depend on stamp-vcl
instead as an optimisation.

Short version:  Yes, your patch looks fine.  It says after importing
changes make sure ltmain.in is uptodate... and when we get round to
building ltmain.sh, make sure it is newer than ltmain.in.

Cheers,
    Gary.
-- Gary V. Vaughan ())_. gary@ {lilith.warpmail.net,gnu.org},address@hidden
Research Scientist   ( '/   http://www.tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/{libtool,m4}
Technical Author   `(_~)_   http://sources.redhat.com/autobook



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


reply via email to

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