"Scott D. Yelich" wrote:
> On 23 Mar 1999, Russ Allbery wrote:
> > Sam <[EMAIL PROTECTED]> writes:
> > > "Standard Solaris machine" is not the same thing as a "Standard UNIX
> > > machine". A standard UNIX machine comes with a functioning C compiler.
> > Solaris doesn't. HP-UX comes with something that's functioning only under
> > the most general possible definition of the term. I don't believe AIX
> > does. IRIX doesn't even come with header files, let alone a compiler.
> > Linux and *BSD come with functioning C compilers.
>
> This may not be the place to ask... and I'm not sure I'd like
> the answers -- but I'll ask anyway:
>
> (1) is it standard (practice) to link cc to gcc? (and who says it is
> standard practice?)
> and
> (2) how many people here have done this?
>
> As far as linking cc to gcc breaking things. I'll provide examples.
> Say, was the SunOS cc ansi compatible? I really do remember
> commany line options to cc that didn't work with gcc and
> vice-versa.
>
> Scott
It is "standard" practice to link cc to your DEFAULT compiler, not always gcc.
However, it often *isn't* done because many people assume cc is always gcc and
pass options to it that shouldn't be passed to it. For example, many egcs
command options are different, like you mentioned with SunOS cc.
I've adminned Solaris for years and I definitely don't have cc linked to gcc.
It causes headaches often, but I typically grep cc * ahead of time if no
autoconf is present... quickly replacing cc with gcc solves things but I must
agree with you, this is NOT the users responsibility to omnisciently know this.
It unquestionably sucks that things are the way they are, but whether you like
it or not, it is how it is. It's stupid. Yup. Can't change that. That's why
documentation is supposed to be detailed and cover things like this. There has
been a lot of stupid clout on this thread, but I think when you get back to
what started it all, it is very legitimate. The documentation might be best to
tell you to configure conf* to suit your needs and leave it at that. Only one
line, noone dies, and Scott's problem is solved...
--
Cris Daniluk [EMAIL PROTECTED]
-------------------------------------------------------------
Digital Services Network, Inc. http://www.dsnet.net
1129 Niles-Cortland Road, Warren, Ohio 44484 [EMAIL PROTECTED]
(330) 609-8624 ext. 20 Fax (330) 609-9990
The Web Hosting Specialists
-------------------------------------------------------------
