[Top][All Lists]

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

Re: Bug in config.status (autoconf 2.49b, test 21)

From: Akim Demaille
Subject: Re: Bug in config.status (autoconf 2.49b, test 21)
Date: 15 Jan 2001 19:00:11 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Crater Lake)

| > Tim> foo=`{ (exit 1); exit; }` || echo fail
| > Tim> DOESN'T (at least on my system). 

As a matter of fact, this is somewhat wrong.  If a plain

foo='exit 1' || echo fail

works as expected, we're outta trouble.

| > We have already discussed about such failures on the Autoconf list,
| > and people reported that such a broken shell can hardly be supported
| > (this occurrence is certainly not the only one).
| Well, it's only this specific instance where the { (exit 1); exit; }
| contruct fails; in all the other places it works fine.

In fact, I'm a bit lost.  Where did you see this construct exactly?

| > What shell are you running?
| The DJGPP port of bash 2.04.
| If you're sure this is a problem with bash, I'll certainly report this
| to the maintainer of the port.

~/src/ace % bash                                                 nostromo 18:33
bash-2.04$ foo=`{ (exit 1); exit; }` || echo fail
bash-2.04$ uname -a
Linux nostromo 2.2.17 #1 Sat Sep 9 12:42:22 EST 2000 i686 unknown
bash-2.04$ exit

There is a problem with the port.

reply via email to

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