X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Message-ID: <COL101-W3355765BD69EBD03BFDE38E6820@phx.gbl>
X-Originating-IP: [76.121.182.92]
From: Jay <jayk123 AT hotmail DOT com>
To: <djgpp AT delorie DOT com>
Subject: quoting PATH_SEPARATOR in config.site?
Date: Tue, 29 Jul 2008 09:00:14 +0000
Importance: Normal
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
X-OriginalArrivalTime: 29 Jul 2008 09:00:14.0391 (UTC) FILETIME=[83B1CC70:01C8F159]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m6T90FWu015289


It seems to me there is a major bug in the 2.03 bash release(s).

where config.site says:

 PATH_SEPARATOR=;  

it should say:

 PATH_SEPARATOR=";"
or
 PATH_SEPARATOR=';'

Because of this, probes for executables fail, such as autoconf 2.57's looking for awk, perl, m4, etc.

 I am less sure as well, that quotes are needed in all the configure scripts on: 

 IFS=$PATH_SEPARATOR 

I was seeing IFS become empty instead of ;.
Without the quotes ; is the end of the command rather than the value of the variable.

v2.04 apparently supports PATH_SEPARATOR=: though I haven't yet found how.

 - Jay