[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The commands report "Bad file number" when read pipes stdin
|
From: |
Chet Ramey |
|
Subject: |
Re: The commands report "Bad file number" when read pipes stdin |
|
Date: |
Thu, 02 Oct 2014 10:52:43 -0400 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 10/2/14, 4:46 AM, Владимир Белоусов wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: mingw32
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE='mingw32' -DCONF_MACHTYPE='i686-pc-mingw32'
> -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale' -DPACKAGE='bash'
> -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -g -O2
> uname output: MINGW32_NT-6.1 BELOUSOV 1.0.18(0.48/3/2) 2012-11-21 22:34
> i686 Msys
> Machine Type: i686-pc-mingw32
>
> Bash Version: 4.3
> Patch Level: 28
> Release Status: release
>
> Description:
> The commands that read pipe stdin report: "Bad file number"
>
> Repeat-By:
> echo "hello" | cat
> or
> echo "hello" | read
I can't reproduce this, so I suspect it's a mingw-specific problem.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/