[Top][All Lists]

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

Re: libtoolize 2.2.7a is a fork bomb under OpenSolaris

From: Peter Rosin
Subject: Re: libtoolize 2.2.7a is a fork bomb under OpenSolaris
Date: Sun, 29 Nov 2009 18:28:31 +0100
User-agent: Thunderbird (Windows/20090812)

Den 2009-11-29 07:09 skrev Gary V. Vaughan:
On 25 Nov 2009, at 10:49, Vadim Zeitlin wrote:
I now see the problem better: the function func_dirname_and_basename()
relaunches libtoolize instead of just extracting its dir and base names.
And this happens because ECHO variable is empty because as_echo is not
defined. So it looks like it _was_ my own fault after all, sorry for the
trouble :-( I guess as_echo is only defined by autoconf 2.62, isn't it?

Anyhow, replacing as_echo with just "echo" makes libtoolize work for me.

Since we have at least two similar reports of this problem (pilot error or 
otherwise), it makes me think that we could make life easier for everyone if we 
either default as_echo to some sensible fallback, or at least fail early once 
libtool detects that as_echo is unset?

For the record, I know I did try to bootstrap my br0ken checkout
with autoconf 2.61 (and possibly I even tried make before noticing
the mistake) before upgrading to 2.64 (I upgraded from debian lenny
to debian squeeze), but I'm fairly certain that I did bootstrap
again with 2.64 after upgrading. I don't know if bootstrapping
should get me out of the mess that appears to have been the result
of the prior actions...


They are in the crowd with the answer before the question.
> Why do you dislike Jeopardy?

reply via email to

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