Mail Archives: djgpp/2001/07/25/22:15:18
Tim Van Holder <tim DOT vanholder AT falconsoft DOT be> wrote:
> Yes, bash has several workarounds for such issues, but I've tried
> very hard to get these things supported by autoconf directly so they
> will no longer be needed for configure scripts. Aside from proper
> executable extension support (which may make it into autoconf 2.53
> mainline, and is already present in the 2.50 DJGPP release), that is
> now the case.
I.e. nobody should have to run autoconf-2.50 on their own, just to be
able to compile existing Unix sources with a 2.50-generated configure
script, right? IOW: the only persons really needing the autoconf-2.50
port for DJGPP would be program authors using DJGPP to maintain
Unix-native packages, then.
I like that prospect.
>> No, it isn't. autoconf-2.50 is a beta release,
> autoconf 2.50 is NOT a beta release.
Sorry to cause confusion, here. You're right, of course. In fact, it's
not autoconf-2.50 itself that's not officially released. Looks like I
let myself be mislead by a broken mirror of www.gnu.org not mentioning
any autoconf release at all.
It's automake and libtool that cause problem, instead. AFAIK, there is
no official version of automake yet that correctly works in
conjunction with autoconf-2.50.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -