From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: RE: Fetish.pm band-aid (Fileutils testsuite)
Date: Wed, 7 Mar 2001 18:43:17 +0100
Message-ID: <CAEGKOHJKAAFPKOCLHDIIEFJCBAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <3AA55AC9.B6A954A1@phekda.freeserve.co.uk>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Will the DJGPP port of autoconf 2.50 ship with config.site? Or is it
> "owned" by the bash distribution at the moment? Will the bash 2.04
> distribution need updating once autoconf 2.50 is out with a new
> config.site?
I plan to include a config.site with autoconf 2.50. Very little needs
to be set there; this is the current "standard" config.site I'm using
with CVS autoconf:


# For now, we need this - future versions of autoconf will hopefully
# be able to do this right.
TEST_FINDS_EXE=y

# Enable these to avoid typical portability problems
#ac_cv_func_fork=no
#ac_cv_func_mkfifo=no
#ac_cv_func_mknod=no
#ac_cv_func_mmap=no
#ac_cv_func_pipe=no
#ac_cv_func_vfork=no

# By using this, results of configure's program checks will be more portable
PATH="/dev/env/DJDIR/bin;$PATH"

# This is REQUIRED: using simply "/bin/(ba)sh" will NOT work (m4 needs this
# to be a full path with executable suffix)
SHELL=/dev/env/DJDIR/bin/bash.exe
CONFIG_SHELL=$SHELL


The TEST_FINDS_EXE will probably be unecessary from 2.51 onwards; there
are plans to add some other means to autoconf to properly detect executables
(probably an external script that can be maintained separately).