Date: Thu, 4 Mar 1999 14:18:59 +0100
From: Laszlo Molnar <laszlo DOT molnar AT eth DOT ericsson DOT se>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: Richard Dawe <richdawe AT bigfoot DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: Perl 5.004/5.005 compilation problems
Message-ID: <19990304141859.B9653@duna91.eth.ericsson.se>
References: <36DD9A38 DOT 8A754FF4 AT meridian22 DOT net> <Pine DOT SUN DOT 3 DOT 91 DOT 990304120751 DOT 1354L-100000 AT is>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.17i
In-Reply-To: <Pine.SUN.3.91.990304120751.1354L-100000@is>; from Eli Zaretskii on Thu, Mar 04, 1999 at 12:09:22PM +0200
Reply-To: djgpp-workers AT delorie DOT com

On Thu, Mar 04, 1999 at 12:09:22PM +0200, Eli Zaretskii wrote:
[..]
> > 126,128c126,128
> > < if (PATH=.; alias -x) >/dev/null 2>&1; then
> > <               inksh=true
> > < fi
> I think I know what happens here.  The ported Bash runs parenthesized
> commands in the same process (because there's no fork), so any changes
> done there propagate into the script.  Replace (foo) > /dev/null with
> `foo > /dev/null`, and it should work.
> Laszlo, how does this work for you?  (I haven't myself built this 
> version of Perl yet.)

I don't know :-) I'm not too familiar with bash scripts, but the bash
version I use (1.14.7.2 or something like this) has no problems with
this. I'm not sure about perl 5.005_02, but 5.004_02 was successfully
built by the stock 1.14.7 bash by several people.

Another workaround would be that Richard sends me his library &
headers, and I'll configure perl for him.

Laszlo