From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Building gdb 5.0
Date: 28 Jun 2001 11:55:38 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 14
Message-ID: <9hf5vq$mka$1@nets3.rz.RWTH-Aachen.DE>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010627175927 DOT 1111H-100000 AT is> <Xns90CD8E76B7A73Xx386xX AT 130 DOT 133 DOT 1 DOT 4>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 993729338 23178 137.226.32.75 (28 Jun 2001 11:55:38 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 28 Jun 2001 11:55:38 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

386sx <386sx AT my-deja DOT com> wrote:

> Apparently it's better to just undefine CDPATH when compiling just to be on 
> the safe side:

Or maybe someone should convince the BASH maintainers that CDPATH
should unconditionally be disregarded in non-interactive shells. It's
a feature meant to ease interactive shell usage, exclusively. I can't
imagine any (sane) shell script to rely on using CDPATH for anything,
so such a change won't break anything that wasn't silently broken
before.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.