Date: Sun, 31 Dec 2000 12:20:29 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: "Tim Van Holder" Message-Id: <3791-Sun31Dec2000122028+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 CC: djgpp-workers AT delorie DOT com In-reply-to: Subject: Re: Ribust shell-based test for DJGPP? References: 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 > From: "Tim Van Holder" > Date: Fri, 29 Dec 2000 18:45:30 +0100 > > * at the end of configure, so I can run dtou on config.status > * in autoupdate, so I can run dtou on the updated configure.in > * in autoheader, so I can run dtou on the output file > * in autoconf, so I can close the output file (exec 4>/dev/null) and run dtou on it Why do you need to run dtou? It shouldn't be required with Bash 2.03 and later (and you are going to require the latesrt Bash to support /dev/env anyway). > So, this will likely be better: > > if test -d /dev/env/DJDIR -a -n "$DJGPP" -a -f "$DJGPP"; then > # Hooray! DJGPP! > fi Is the DJGPP variable set in the case when you are cross-compiling?