Re: compilers

[Jean Francois Martinez <jfm2@xxxxxxxxxxxxxxxx>]

Adam Cioccarelli wrote:
> 
> In what way?
> 
> I have been using gcc 3.0 and gcc 3.0.2 for some time now without any
> problems...
> 

That is until you compile/use the wrong module.  Do an "rpm -ba
kernel.spec"
in order to ensure you compile everything or about evrything.  (And hack
the
SPEC file for forcing use of gcc).  In Linux's history there has been no
case
of a new compiler not breaking kernel.  Not necessarily compiler's fault
since
there is non compliant code rejected by newer compilers (they also
happen to be
more compliant) and some cases where kernel code relies on compiler not
being
too smart.


> Adam
> 
> Jean Francois Martinez wrote:
> 
> > Austin Gonyou wrote:
> >
> >>This is not true. RH 7.1 gcc is not broke(as in can't compile code that
> >>runs), but there was an update to it which fixed certain issues. You
> >>definitely CAN compile kernels with that default gcc though that will
> >>boot. Will you have problems? ymmv. The best course of action is to
> >>either get gcc3, or update your current gcc from updates.redhat.com.
> >>
> >>
> >
> > Gcc3 is known to NOT work with kernel.
> > 
> >

-- 
Jean Francois Martinez

Project Independence http://independence.seul.org
Because Linux should be for everyone