From: cgf AT cygnus DOT com (Christopher G. Faylor)
Subject: Re: ncurses
28 Dec 1998 15:35:22 GMT
Message-ID: <7688fq$aj8$1@cronkite.cygnus.com>
References: <001101be3011$97efb940$4f2574c0 AT PCX DOT gefen DOT co DOT il> <m2iuey9fl1 DOT fsf DOT cygnus DOT gnu-win32 AT forest DOT nuthouse DOT au>
X-Newsreader: trn 4.0-test63 (15 March 1998)

In article <m2iuey9fl1 DOT fsf DOT cygnus DOT gnu-win32 AT forest DOT nuthouse DOT au>,
Peter Moulder <reiter AT netspace DOT net DOT au> wrote:
>Paul Wilson <fwibbly AT earthlink DOT net> writes:
>> The problem with some GNU configure utils is that they pipe their
>> commands to /dev/null. Last I tried to create a /dev/null using mknod, I
>> couldn't create it with the exact major and minor device numbers, so
>> creating /dev/null won't fix the problem. Just edit out the >/dev/null
>> from the configure script where configure checks for gcc.
>
>On b20.0 / NT, /dev/null does work even if ls doesn't see it.
>
>Try doing `sh -x configure' instead of `./configure', to see what it
>is trying to do and why it thinks gcc doesn't work.
>
>(You might try Paul's suggestion first, though, just to check whether
>I'm speaking garbage.)

Actually, /dev/null has worked for some time.  As noted, you can't do a
'ls -l /dev/null' but we're working on that.
-- 
cgf AT cygnus DOT com
http://www.cygnus.com/