From: 386sx <386sx AT my-deja DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Building gdb 5.0
Date: 29 Jun 2001 08:29:33 GMT
Organization: not a chance
Lines: 38
Message-ID: <Xns90CF2DB2D8B92Xx386xX@130.133.1.4>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010628131316 DOT 12284F-100000 AT is> <Xns90CF2B576F622Xx386xX AT 130 DOT 133 DOT 1 DOT 4>
NNTP-Posting-Host: r-93.63.alltel.net (166.102.93.63)
X-Trace: fu-berlin.de 993803373 14387778 166.102.93.63 (16 [33304])
User-Agent: Xnews/4.06.22
X-Hobbies: X-Pickup-Sticks,  X-Polo-Wrestling
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:

> Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> 
>> On 27 Jun 2001, 386sx wrote:
>> 
>>> > I can't imagine people could do that in their CDPATH, since if they
>>> > do, "cd foo" cannot chdir into a subdirectory `foo' of the current
>>> > directory. 
>>> 
>>> True only if there is a "foo'' subdirectory within a directory in
>>> CDPATH. If "." isn't included in CDPATH cd acts as if "." were the
>>> last entry. 
>> 
>> Then why did "cd intl" fail in the GDB build procedure?
>> 
>> It sounds like I didn't really understand the reason for this problem,
>> so please tell some more about this.  Since this issue is not specific
>> to DJGPP, it will probably require some changes in the GDB configure
>> scripts, and I'd like to be able to explain this to the GDB
>> maintainers. 
> 
> I think the answer is not the interactive bash, but bash's POSIX 
> non-interactive alter-ego (SHELL=/bin/sh)

I haven't tried to compile GDB in about a year but as I said I ran into 
problems trying to compile other programs on Linux due to CDPATH not having 
"." as the first entry, and indeed I found that when I explicitly do:

$ make SHELL=/bin/bash 

the problem disappears.

 -- 
386

clc FAQ:
http://www.eskimo.com/~scs/C-faq/top.html