From: Keetnet AT wilmington DOT net (Keet)
Subject: b17 bash problem with /dev/null on Windows 95 system
7 Dec 1996 23:03:23 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <1.5.4.32.19961208055028.00670d98.cygnus.gnu-win32@wilmington.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: keetnet AT wilmington DOT net
X-Mailer: Windows Eudora Light Version 1.5.4 (32)
Original-To: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

>
>  COPY FOR DUP FAILED, handle in FFFFFFFF 6!!
>  bash.exe: /dev/null: Bad file number
>
>Can anyone else reproduce this?  If so, do you know of a fix?  If not,
>does anyone have suggestions about how to debug it?  Should I look at
>bash or is the problem more likely in cygwin.dll?
>
>Thanks,
>
>jwe

amazingly enough, i can reproduce this error on my machine.. running, you
guessed it, a configure script. when it finishes, it was supposed to have
updated the makefile, the configure.in, and autconf.h.in, to include all the
lovely little tools it could find, yet it doesn't seem to do this. i can't
find a fix for it, so i just manualy edited the makefile.in and compiled,
but if there is a fix for this, or i'm missing something, please clue me in
as what to do.

Thanks,

- Keet
keetnet AT wilmington DOT net


-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".