Path: utzoo!telly!attcan!ncrcan!scocan!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.unix.i386
Subject: Re: SCO Unix Blank Compiler Error Messages
Message-ID: <1990Aug26.145023.25570@sco.COM>
Date: 26 Aug 90 18:50:23 GMT
References: <11@raider.mfee.tn.us> <1990Aug16.215542.2958@tijc02.uucp> <1990Aug20.235609.1843@sco.COM> <751@mecky.UUCP>
Reply-To: seanf@sco.COM (Sean Fagan)
Distribution: comp
Organization: The Santa Cruz Operation, Inc.
Lines: 21

In article <751@mecky.UUCP> walter@mecky.UUCP (Walter Mecky) writes:
>What about "cc.err"? There is one in /lib but not in /lib/386. Does
>the "cc" command not use it? If I had such a line in /etc/default/cc:
>
>	FLAGS=-M3 # comment
>
>I only get "Command line warning D4002 : " from "cc". No message,
>even if I linked /lib/cc.err in /lib/386. Is this ok, Sean?

Yes.  There's a ... misfeature in the code for /bin/cc:  it opens up
/etc/default/<whatever> before it sets up the error file.  Thus, it has
nothing to look for!  (I'm going to change this, and see if it breaks
anything 8-).  It shouldn't, though.)

cc wants /lib/cc.err, not /lib/386/cc.err, btw.

-- 
Sean Eric Fagan  | "let's face it, finding yourself dead is one 
seanf@sco.COM    |   of life's more difficult moments."
uunet!sco!seanf  |   -- Mark Leeper, reviewing _Ghost_
(408) 458-1422   | Any opinions expressed are my own, not my employers'.