Our mails crossed, yes. I just submitted a bash bug report because other
things on the system were breaking with the new version. Not sure which
end is supposed to get fixed, but at least everyone knows now. :)

On Mon, Nov 04, 2002 at 12:21:21AM -0800, Randolph Chung wrote:
> > ldd run on any file returns "./: No such file or directory".
> 
> the bug is somewhat dependent on the version of bash you are using.
> Apparently 2.05b-3 was ok, but 2.05b-4 broke it.. but I'm not sure what
> ldd is doing is correct. The offending line is line 113 of ldd:
> 
>     113 for file do
>     ....
> 
> i'm no posix expert, but that looks strange to me.  changing that to 
> 'for file in $@; do' ... works, and seems to be more "standard"..
> 
-- 
Conrad Heiney
[EMAIL PROTECTED]
http://fringehead.org
----------

GO AND TELL ENGLAND THAT SCOTLAND IS RESISTANT TO STAINS!

Attachment: msg01688/pgp00000.pgp
Description: PGP signature

Reply via email to