From: pjfarley3 AT escape DOT com (Peter J. Farley III)
Newsgroups: comp.os.msdos.djgpp
Subject: autoconf 2.50 question -- still need to run against unix scripts?
Message-ID: <3b5e44be.33943055@news.escape.com>
X-Newsreader: Forte Free Agent 1.21/32.243
Lines: 18
NNTP-Posting-Date: Tue, 24 Jul 2001 23:06:33 CDT
Organization: Giganews.Com - Premium News Outsourcing
X-Trace: sv3-9sw5iq+H0DQD3zMumXZAS2Bk9a4nUrz2WXHJgaZ7R8QWU73y6k6af70jecc+yjMpoxQw/sAx31zju2O!qWLP/nhbsQ819sJbTGCQxi3Vj2cVt9W0diyXMC/NPn6UuMZwZAUM5pw733NQo8n+
X-Complaints-To: abuse AT GigaNews DOT Com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-Info: Please be sure to forward a copy of ALL headers
X-Abuse-Info: Otherwise we will be unable to process your complaint properly
Date: Wed, 25 Jul 2001 04:11:06 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

In the past, running DJGPP autoconf against previously unix-only
configure scripts was advised to permit various unixy tests
(especially the notorious test for executables with no "EXE_EXT"
macros used) to work cleanly.  Additional problems supporting DOS PATH
conventions of using ";" vs unix ":" for separators were also resolved
by re-creating the configure script with DJGPP autoconf.

With the advent of autoconf 2.50 and the more recent port of bash
2.04, is it still advisable to re-run autoconf on unix-developed
source packages to re-create the configure script?  Or can this step
now be bypassed, and unix-made configure scripts run as-is?

Any RTFM's, gothcas or advice appreciated.


----------------------------------------------------
Peter J. Farley III (pjfarley AT nospam DOT dorsai DOT org OR
                     pjfarley3 AT nospam DOT escape DOT com)