From: 386sx <386sx AT my-deja DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Building gdb 5.0
Date: 26 Jun 2001 15:11:39 GMT
Organization: not a chance
Lines: 44
Message-ID: <Xns90CC71DFED432Xx386xX@130.133.1.4>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010626161059 DOT 17201A-100000 AT is>
NNTP-Posting-Host: asoh3pp19.alltel.net (166.102.93.84)
X-Trace: fu-berlin.de 993568299 13215580 166.102.93.84 (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

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:

> 
> On 25 Jun 2001, 386sx wrote:
> 
>> > Configuring intl...
>> > /usr/tmp/gdb-5.0/configure: cd: intl: No such file or directory
>> > (ENOENT) 
>> 
>> I thought this was a djgpp problem until I got Linux and ran into a
>> similar problem during compilation. It turns out that the culprit in
>> the Linux case was the CDPATH environment variable. When I unset it
>> everything goes fine. 
>> 
>> Since I also had CDPATH set in the djgpp case, perhaps CDPATH was the 
>> culprit then too. Mystery finally solved? 
> 
> Thanks for following up on this.
> 
> It's possible that CDPATH is the culprit, but only of "." is not part
> of its value.  I don't think that is the case, since then you won't be
> able to say "cd foo" and get what you expect.

Indeed that was the case. "." was not in my CDPATH. Now it is. :)
Problem solved -- thank you.

> So, could you please post more info?  What is the value of CDPATH on
> your system, and how does this prevent Bash from chdir'ing into the
> intl directory?  

The value was '$HOME/work:$HOME' which I got from '${HOME}/work;${HOME}'
which was the default setting in the example _bashrc that came with djgpp;
apparently a bug?

> Can you "cd intl" interactively from the top-level directory where you
> unpacked GDB sources?

Yes I could.

-- 
386

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