Message-ID: From: "Andris Pavenis" To: Alexandre Oliva , Andris Pavenis , "Mark E." , autoconf AT gnu DOT org Date: Wed, 13 Jan 1999 12:58:46 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: patch for autoheader.sh CC: "Mark E." , autoconf AT gnu DOT org, djgpp-workers AT delorie DOT com References: "Gary V. Vaughan"'s message of "Wed, 13 Jan 1999 10:19:03 +0000" In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01d) Reply-To: djgpp-workers AT delorie DOT com On 13 Jan 99, at 8:37, 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 :-( > One slightly different suggestion (should be more portable than /dev/null). 'exec 1>&2' instead of 'exec >/dev/null' Tested in DOS session under Win95 (DJGPP compiled bash) where I initially met sharing problem and it works. I even tried running 'autoheader 2>&1' for slight torture and also no problems. > > 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. > Better let them broken until Cygnus fixes cygwin, if this is really > broken. > Andris