From:	M DOT A DOT Bukin AT inp DOT nsk DOT su
To:	djgpp AT delorie DOT com
Subject:	Re: /dev/null problems with bash when rebuild from sources
References:	<Pine DOT GSO DOT 4 DOT 05 DOT 9810020916001 DOT 26036-100000 AT rtbsci146s>
Date:	03 Oct 1998 20:49:35 +0700
In-Reply-To:	Olivier Perron's message of "Fri, 2 Oct 1998 09:19:22 +0200 (MET DST)"
Message-ID:	<20zpbdwya8.fsf@Sky.inp.nsk.su>
Lines:	28
X-Mailer:	Gnus v5.5/Emacs 19.34

Olivier Perron <perron AT art DOT alcatel DOT fr> writes:

> On Thu, 1 Oct 1998, Eli Zaretskii wrote:
> 
> > On Tue, 29 Sep 1998, Olivier Perron wrote:
> > 
> > > With that version of bash, if I type: echo "foo" >/dev/null
> > > I have the following error: bash: /dev/null: No such file or directory
> > > (ENOENT)
> > 
> > This is a bug in stock v2.01 libc.a.  Get the patched libc (see the
> > FAQ for a URL), rebuild Bash, and this problem should go away.
> > 
> > (The bug is in the function `_truename' that is called by `stat': the
> > version bundled with stock v2.01 didn't support /dev/foo names.)
> > 
> Yes, but I do *have* the patched libc with the _truename *you* gave me a
> couple of weeks ago when I had to rebuild bash !
> So, I'm completly lost !

It can be related to `SYSROOT' environment variable.  At least, if I
set SYSROOT to the DJDIR, bash can not find /dev/null, but can find
/bin/sh.  And if I remove SYSROOT var., bash finds /dev/null, but not
/bin/sh.  I don't remember which version of bash I use (maybe it was
built with unpatched _truename).

-- 
Michael Bukin

- Raw text -