Re: botched configure check for /dev/stdin

2006-11-15 Thread Chet Ramey
Paul Jarc wrote: > Chet Ramey <[EMAIL PROTECTED]> wrote: >> Hardcoding `/bin/test' is a tricky business: > > How about "(exec test ...)"? Or "env test ..."? Yeah, I considered the first variant. Something like (exec test -r /dev/fd/3 3http://cnswww.cns.cwru.edu/~chet/

Re: botched configure check for /dev/stdin

2006-11-15 Thread Paul Jarc
Chet Ramey <[EMAIL PROTECTED]> wrote: > Hardcoding `/bin/test' is a tricky business: How about "(exec test ...)"? Or "env test ..."? paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Re: botched configure check for /dev/stdin

2006-11-15 Thread Chet Ramey
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 configuring with a version of bash that already