[Top][All Lists]

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

Re: ZILE 2.3.10 (Autoconf 2.64 finds deadly DJGPP Bash bug)

From: Rugxulo
Subject: Re: ZILE 2.3.10 (Autoconf 2.64 finds deadly DJGPP Bash bug)
Date: Thu, 20 Aug 2009 18:18:29 -0500

Hi, good news!    :-)

On Thu, Aug 20, 2009 at 5:14 PM, Reuben Thomas<address@hidden> wrote:
> 2009/8/20 Rugxulo <address@hidden>:
>> I already added "_zile" support, it wasn't hard. But if you have a
>> better way ....
> Using autoconf macros is a bit cleaner, as it sweeps the
> platform-specific aspect under the carpet.

Whatever works.

>> Yes, it does build, but only if you get past "./configure" !! This is
>> a very very difficult problem for me.
> Sure :(

My own inexperience plus lack of decent error message plus lack of
help surely makes this extremely difficult. I can't stress this

>> 3). Find the problem and patch DJGPP Bash and expect everyone to
>> upgrade (not the worst idea, and I'm 100% sure I know where the
>> problem is, but I don't know where/how to fix it)      :-/
> That's what I'd describe as "the Right Thing To Do".

Anything to fix the problem!!

>> 4). Get you (ZILE maintainer) to downgrade to 2.63
> Not going to happen, first because I have to use what I get (and 2.64
> will be in Ubuntu in a couple of months); secondly because there's not
> a bug in autoconf as far as I can see; thirdly because 2.64 is
> necessary to FIX one DOS-related bug.

First of all, 2.63 was "good enough" for quite a while, so I don't
consider it much of a regression to use it for the near future. And
just because Ubuntu uses something doesn't make it perfect. Second,
and I say this with admiration, AutoConf is FULL of workarounds for
buggy shells. Sure, sticking to a standard is good, but let's be
pragmatic, nobody is perfect. And third, no, the bug you mention is a
one-char typo that anybody (!) can fix manually.

But all that's moot because I found a way around the problem (yes!!!).

For whatever reason, "./configure" (produced by 2.64) uses "return
$ac_retval" in five spots, and that's where it crashes ("checking for
GNU C compiler ...") for no good reason, and on Vista without even
reporting the GPF crash dump!

Workaround? Add parentheses around it.

sed -i -e '/return \$ac_retval/s//( & )/' configure

I have tested both DJGPP 2.03p2 and 2.04 (with my local ZILE hacks, of
course), and it now builds again for 2.3.10. Rejoice!!   :-)

>> P.S. More good news:  C-x C-v still seems broken, even in Cygwin.   :-/
> Can you give me precise instructions to reproduce it, please?

I'll have to rebuild later under Cygwin and e-mail you off-list.
Suffice to say that starting up and immediately using "C-x C-v"
doesn't work for me (silent crash).

reply via email to

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