Re: gcc or cc?
When considering poratibility and code cleaness, the only answere one
can give to this question is "CC=cc".
No sourcecode should rely on gcc or any of its extensions. And if it
doesn`t use any gcc specific stuff, it should not rely on gcc.
A rule to use gcc or a garanty that cc will be gcc on all systems just
makes people take that as a fact and use it. The result is code that
realy relies on gcc, but doesn`t say so and thus the code will not
work on a different setup or different unix.
Look at g++, which is now replaced by eg++. The only thing that made
the change difficult, where (and I think still are) some packages that
use obscure stuff, that was g++ Vx.x.x specific (well, and some small
bugs). If Debian starts garantying that cc is gcc it next has to
garanty that gcc is gcc V<insert some completly obsolete version here>
and nothing else.
May the Source be with you.
Goswin
Reply to: