RE: Question concerning configure scripts

["Parker, Ron" <rdparker at butlermfg dot org>]

I have had this problem with some configure scripts as well.  The exact
nature of the problem was that the system was trying to stat()
/dev/null.  Which does not actually exist.  My solution was to use the
standard command prompt to create an almost empty file.

On my machine E:\Unix is mounted as root, "/". So I did the following:
	e:
	cd \unix
	mkdir dev
	echo.>dev\null

Using the period immediately following "echo" cause echo to output an
empty line.  This gives a two-byte, CR/LF, /dev/null file that can be
stat'ed.

-----Original Message-----
From: Alexander Stockdale [mailto:astockdale@computer.org]
Sent: Tuesday, June 16, 1998 8:07 AM
To: gnu-win32@cygnus.com
Subject: Question concerning configure scripts


I asked this question before, but received no response.  Has anyone 
else experienced problems with the use of /dev/null in configure 
scripts?  In particular I find I have problems with gcc -E commands 
if the STDERR is piped to /dev/null.  I work around it by changing 
/dev/null to a junk file, which allows me to proceed.  Anyone have 
any ideas?
Alexander Stockdale

-
For help on using this list (especially unsubscribing), send a message
to
"gnu-win32-request@cygnus.com" with one line of text: "help".

application/ms-tnef