From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>, "Mark E." <snowball3 AT bigfoot DOT com>
Subject: RE: New bash 2.04 beta release
Date: Tue, 10 Apr 2001 00:14:03 +0200
Message-ID: <CAEGKOHJKAAFPKOCLHDIMEEFCCAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0000_01C0C153.26349340"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <8011-Tue10Apr2001000906+0300-eliz@is.elta.co.il>
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

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C0C153.26349340
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> > From: "Mark E." <snowball3 AT bigfoot DOT com>
> > Date: Mon, 9 Apr 2001 16:12:09 -0400
> >
> > I'd also like know what changes should be made to config.site
> for the next
> > Autoconf release. Any thoughts on making config.site its own
> package? It's
> > contents depend both on Bash and Autoconf so a change in either means a
> > potential update of that file.
>
> How about making config.site part of borth packages?
Generally a good idea, IMHO - that way, autoconf can be updated without the
need to update bash, so people using a new autoconf can override the
standard one that comes with bash.

Attached is the config.site needed for the current CVS autoconf to run
fine; this will be included in the DJGPP package for autoconf 2.50

Note that the ac_executable_extensions is a hack to avoid depending on
smart 'test -f' handling (EMX's bash doesn't have it).
autoconf 2.51 will most likely
a) handle this more gracefully
b) deduce the list by itself

------=_NextPart_000_0000_01C0C153.26349340
Content-Type: application/octet-stream;
	name="config.site"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="config.site"

# For now, we need this - future versions of autoconf will hopefully
# be able to do this right.
# TEST_FINDS_EXE=3Dy
ac_executable_extensions=3D".exe .com .bat .btm .sh .ksh .pl .sed"

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

# By using this, results of configure's program checks will be more =
portable
PATH=3D"/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=3D/dev/env/DJDIR/bin/bash.exe
CONFIG_SHELL=3D$SHELL

------=_NextPart_000_0000_01C0C153.26349340--