Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!sdsu!crash!pnet01!cwr
From: cwr@pnet01.cts.com (Will Rose)
Newsgroups: comp.os.minix
Subject: Compiling 1.5.0 commands
Message-ID: <1552@crash.cts.com>
Date: 18 Feb 90 06:56:02 GMT
Sender: root@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 38

In a recent article, nfs@notecnirp.UUCP (Norbert Schlenker) writes:
 
>An extraordinary number of commands generate warnings when compiled,
>most of which are caused by the definition of NULL as ((void *)0).
 
This is very odd indeed.  I put the net 1.5.0 patches on the PH 1.3
upgrade distribution, using a PC XT clone, and got only the following
warnings when compiling the commands (I didn't have the fp or string
libraries installed):
 
chgrp.c
"chgrp.c", line 64: (warning) incompatible pointers in ==
 
compress.c
"compress.c", line 1499: (warning) conversion of long to pointer
        loses accuracy
 
This doesn't include those commands, such as Mined and the shell,
that have their own subdirectory, but I can't remember them producing
a lot of messages.
 
Where are the errors coming from - the old (1.2?) compiler, a missing or
scrambled header file, or what?  The NULL definition is in a lot of headers,
so I can't believe my compiler missed it.  I used the flags -D_MINIX and
-D_POSIX_SOURCE fairly liberally; perhaps that's the answer.
 
Curioser and curiouser - Will
 
-----------------------------------------------------------------------
"If heaven too had passions  | Will Rose
     even heaven would       | UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!cw
     grow old."  -  Li Ho.   | ARPA: crash!pnet01!cwr@nosc.mil
                             | INET: cwr@pnet01.cts.com


UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!cwr
ARPA: crash!pnet01!cwr@nosc.mil
INET: cwr@pnet01.cts.com