[Top][All Lists]

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

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

From: Peter Ekberg
Subject: RE: config.status (or something) writes out a crippled libtool script
Date: Mon, 29 Aug 2005 12:26:59 +0200

Ralf Wildenhues wrote:
> > > > 10. make
> > > [ triggers ltmain.m4sh -> ltmain.sh recreation ]
> > > > /bin/sh: autom4te: command not found
> > > *snip*
> > > 
> > > Thanks for this report.  Can you try the attached patch?  
> It has the
> > 
> > Seems to work nicely. Thanks!
> Yet it's the wrong fix.  Again.  
> Last time it needed Alexandre to remind us:  No system-specifics may
> up in ltmain.sh!  Why?  It's used by clients when they libtoolize.

There seems to indeed be something missing, but I don't know
if the following is what you are referring to, so I'm just
doing this report on the odd chance that it isn't...

It (crippled libtool script) still happens from time to
time. I *think* it happens when I do a change to e.g.
libtool.m4 and then forget to bootstrap and just run
configure in MSYS (where I don't have autotools). After
that, I get a borken libtool script. Simply trying to
bootstrap (in Cygwin) after such a mistake does not help,
but thanks to your patch I have figured out that touching
libltdl/config/ltmain.m4sh followed by bootstrap does the


reply via email to

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