[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: botched configure check for /dev/stdin

From: Chet Ramey
Subject: Re: botched configure check for /dev/stdin
Date: Wed, 15 Nov 2006 11:31:11 -0500
User-agent: Thunderbird (Macintosh/20061025)

Eric Blake wrote:

> Machine Type: i686-pc-cygwin
> Bash Version: 3.2
> Patch Level: 5
> Release Status: release
> Description:
>         The configure check for whether /dev/stdin is available is flawed,
> since it invokes 'test -r /dev/stdin </dev/null'.  However, when
> configuring with a version of bash that already fakes /dev/stdin, this
> means that the next configure run on bash will assume that /dev/stdin.
> Fix:
>         Apply this patch and rerun autoconf before configuring.  Using
> /bin/test instead of test bypasses the bash builtin, and thus bypasses an
> installed bash's internal special-casing of /dev/stdin.

Thanks.  I've been looking at different solutions to this for a week or
two.  Hardcoding `/bin/test' is a tricky business:

jenna.ins.cwru.edu(1)$ ls -l /bin/test
/bin/ls: /bin/test: No such file or directory
jenna.ins.cwru.edu(1)$ uname -a
Linux jenna.ins.cwru.edu 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686
i386 GNU/Linux

Even going through a list of likely directories isn't that much better.
I might end up just writing a C program to test everything.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                       Live Strong.  No day but today.
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]