From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: Ribust shell-based test for DJGPP?
Date: Thu, 28 Dec 2000 16:31:46 +0100
Message-ID: <NEBBIOJNGMKPNOBKHCGHCEBMCAAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id KAA22363
Reply-To: djgpp-workers AT delorie DOT com

Hi,

I'm updating my patched autoconf to match version 2.49b.
Currently, I'm using the following test to check for DJGPP
in the few places where behaviour needs to differ:

if test -d /dev/env/DJDIR -a -f /dev/env/DJDIR/djgpp.env
then
  # DJ Stuff
else
  # Regular Unix stuff
fi

Now I would like to know whether this is sufficiently
fool-proof; the idea is that this should DTRT both under
Linux/Unix/whatever and under DJGPP (so a DJGPP-patched
configure script will still run normally on all other
systems).
I know it requires a DJGPP 2.03-compiled bash, but other
than that, will this always succeed for a DJGPP system and
always fail for a non-DJGPP one? In particular, is a
DJGPP system _required_ to have the djgpp.env file?

Any suggestions for a more robust, shell-based, test would
be greatly appreciated.