Subject: Re: "cc" vs. "gcc" in current
To: None <gduzan@acm.org>
From: Juergen Hannken-Illjes <hannken@eis.cs.tu-bs.de>
List: tech-toolchain
Date: 12/26/2001 17:00:09
Update, there was an error with gnu/usr.bin/gcc/(un)protoize where
the (un)protoize binaries were installed as gcc.
Both gnu/usr.bin/gcc/Makefile should be at rev 1.3
Reinstalling gcc from gnu/usr.bin/gcc/gcc should also work.
>
> Under current/i386 as of December 20th I'm getting some odd
> behavior from the compiler when invoked as "gcc".
>
> 1.5.3_ALPHA:
>
> ===========================================================================
> wheel { ~ } % gcc -O
> gcc: No input files
> wheel { ~ } % cc -O
> cc: No input files
> ===========================================================================
>
> 1.5ZA (2001-12-20):
>
> ===========================================================================
> capo { ~ } % gcc -O
> gcc: invalid option -- O
> gcc: usage 'gcc [ -VqfnkN ] [ -i <istring> ] [ filename ... ]'
> capo { ~ } % cc -O
> cc: No input files
> ===========================================================================
>
> This shows up in particular when building XFree4, since it is
> set up with "CC=gcc". A "make USE_XF86_4=yes" results in the above
> usage message, while "make USE_XF86_4=yes CC=cc" allows it to
> continue normally. I expect this will be an issue with some packages,
> as well.
> Any ideas what's going on here?
>
> Gary D. Duzan
>
>
>
--
Juergen Hannken-Illjes - hannken@eis.cs.tu-bs.de - TU Braunschweig (Germany)