From: jwe AT bevo DOT che DOT wisc DOT edu ("John W. Eaton")
Subject: Re: b17 bash problem with /dev/null on Windows 95 system
8 Dec 1996 17:35:23 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199612090054.SAA00438.cygnus.gnu-win32@tillamook-sharp.eaton.net>
References: <1 DOT 5 DOT 4 DOT 32 DOT 19961208055028 DOT 00670d98 AT wilmington DOT net>
Original-To: gnu-win32 AT cygnus DOT com
In-Reply-To: <1.5.4.32.19961208055028.00670d98@wilmington.net>
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Yesterday, I wrote about a problem with b17, bash, and /dev/null on a
Windows 95 system.  Some people suggested that it might be caused by
having an old copy of cygwin.dll somewhere but I am quite certain that
I only have files from b17 installed.

In any case, I still have the problem but have since discovered that
although

  bash$ echo foo > /dev/null

fails,

  bash$ echo foo > /dev/nul

works (?!).

So, I kluged my way around the problem by substituting /dev/nul for
/dev/null everywhere, and I was able to build a (sort of) working
Octave binary.  Now on to the other nits...

Thanks,

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