Message-ID: <369C7BB6.DBB43A78@oranda.demon.co.uk> Date: Wed, 13 Jan 1999 10:55:50 +0000 From: "Gary V. Vaughan" Organization: Aethos Communication Systems ltd. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Alexandre Oliva CC: Andris Pavenis , "Mark E." , autoconf AT gnu DOT org, djgpp-workers AT delorie DOT com Subject: Re: patch for autoheader.sh References: <369C7317 DOT E2AE1CBC AT oranda DOT demon DOT co DOT uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Alexandre Oliva wrote: > > On Jan 13, 1999, "Gary V. Vaughan" wrote: > > > Alexandre Oliva wrote: > >> > >> On Jan 13, 1999, Andris Pavenis wrote: > >> > >> > No problems with /dev/null in DJGPP. But I don't know how it > >> > will be with for example CygWin (as I'm not using it). > >> > >> It works. > > > IIRC, cygwin emulates /dev/null properly only on NT. I'm pretty > > sure win95 has problems... not sure about win98. > > It worked for me on win98, and I'm pretty sure it used to work on > Win95 too, but I can't test it any more :-( > > > Time for another configure test? > > Ugh! Better avoid it. /dev/null is so abused that we'd die before > we could replace all uses of it with the result of the configure > test. I don't want to die. Lets not mess with configure then. Perhaps the win95 failure modes are pathological... and we can ignore the problem for the general case? > Better let them broken until Cygnus fixes cygwin, if this is really > broken. IIRC, the cygwin maintainers are aware of the problem, but expect win95 to go out of fashion before they fix it. Cheers, Gary.