From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Question about running configure script
Date:	26 Apr 2000 08:40:45 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	24
Message-ID:	<8e6a2d$7c4$1@nets3.rz.RWTH-Aachen.DE>
References:	<3905B9E3 DOT C6DA3661 AT worldaccessnet DOT com> <8e4ldv$i1u$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <vn3cgssig0vodajeunb5js8c550e86ebgo AT 4ax DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 956738445 7556 137.226.32.75 (26 Apr 2000 08:40:45 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	26 Apr 2000 08:40:45 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Jason Green <news AT jgreen4 DOT fsnet DOT co DOT uk> wrote:
> Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> wrote:

>> There is a pitfall waiting for you, though: 'configure' scripts
>> generated by most (all?) versions of GNU autoconf don't work on DOS
>> unchanged, despite all heroic efforts. 
[...]
> Is it usually obvious if the configure script has failed, or does it
> break quietly?

Both cases happen. It's best to crosscheck all results reported by
'configure' to see if they're correct. It may report an existing
utility program such as 'sed' or 'awk' as missing, or it may state
that certain function don't exist, when in fact they do, or the other
way round.

The latest Bash seems to have improved the situation significantly, as
statet by Prashant in his replies, but you still have to watch its
working closely. GNU autoconf 'configure' scripts are quite a stress
test for DJGPP Bash.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -