From: snowball3 AT bigfoot DOT com (Mark E.) To: djgpp AT delorie DOT com Subject: Re: [ANNOUNCE] DJGPP port of GNU Autoconf 2.13 update 2 Date: Thu, 01 Jul 1999 13:49:15 GMT Organization: Snowball's Web Message-ID: <377d70ad.2567247@smtp1.ibm.net> References: In-Reply-To: X-Mailer: Forte Agent 1.5/32.452 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id JAA21842 Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote: > >On Wed, 30 Jun 1999, Teun Burgers wrote: > >> On cygwin $COMSPEC is also defined. With this patch, >> IFS is set to ; on cygwin causing the search for >> programs to fail there. If : is going to >> ac_test_flag="-f" >> if ! test -z "$COMSPEC$ComSpec"; then >> ac_test_flag="-x" >> fi Yep, probably should have used DJDIR instead of COMSPEC. But unless an official GNU maintainer starts using the DJGPP port to generate configure scripts, it shouldn't be a big problem. > >I'm not sure IFS needs to be changed at all, even if : is not the >default in the DJGPP port of Bash. We can always set PATH_SEPARATOR=: >before running the configure script. Changing IFS might break >something with the DJGPP port as well. In the part of the code in question, IFS is saved, then changed so the PATH variable can be word split, and the saved value of IFS restored. If IFS=":' and PATH_SEPARATOR=";" and IFS isn't changed to PATH_SEPARATOR, the PATH will be split incorrectly. Given PATH=c:/djgpp/bin;c:/windows;c:/windows/command the result of the word split will be: c /djgpp/bin;c /windows;c /windows/command Not what we wanted. This is why IFS is changed to be set according to PATH_SEPARATOR, so PATH is split correctly and whatever file in question has a chance of being found. Mark -- Mark E.: snowball3 AT bigfoot DOT com http://snowball.frogspace.net/