From: John K. Hinsdale <hin@al...> - 2004-12-16 23:00:35
Not sure why, but the addition of
into the top-level "configure" script a couple days ago causes
"configure" to do nothing and exit right away in my environment. I'm
using a very old bash (2.05) that is the default in my Debian "woody"
If a newer bash is required I'll try that. I don't see requiring a
newer shell as unreasonable, esp. if this fixes some bigger problem.
The delay in the update to Debian's latest stable release is so far
behind I'll probably buy new hardware before I am able to or need to
Just wanted to give the heads up it has broken at least one
John Hinsdale, Alma Mater Software, Inc., Tarrytown, NY 10591-3710 USA
hin@... | http://www.alma.com/staff/hin | +1 914 631 4690
From: Bruno Haible <bruno@cl...> - 2005-01-06 16:21:54
John K. Hinsdale wrote:
> Not sure why, but the addition of
> unset CDPATH
> into the top-level "configure" script a couple days ago causes
> "configure" to do nothing and exit right away in my environment. I'm
> using a very old bash (2.05) that is the default in my Debian "woody"
Thanks for the warning. I see that newer versions of automake/libtool
use a more robust idiom. I've put this idiom into clisp's configure now.
Hopefully it works better.