Red Hat 7.0

Brett generica at
Thu Nov 9 23:49:59 PST 2000


On a non lfs issue here,

This has been discussed to death on the lk-ml.
The point is that gcc has to move forward, and doing so will break the
kernel, as the kernel uses a LOT of gcc hacks, which are limited to
certain versions.  This is the kernels fault, not gcc's.  You can't really
expect gcc to say "well, it works, lets stop development" ... its just
that the kernel can't be expected to keep up with gcc developments until
they are stable.

The point is that the gcc in RH7 _can_ (for the most part) be used as a
normal gcc compiler, just not for the kernel.  Which is why kgcc was
included.  I say for the most part, because there are several (sorta
severe) bugs in the shipped gcc.  _This_ part of it is redhats fault,
which they freely admit.

Just clearing up the fact that rh7 can compile things properly.  If gcc
gives you problems, use kgcc... no biggie.

	/ Brett

On Thu, 9 Nov 2000, Jesse Tie Ten Quee wrote:
> Yo,
> On Thu, Nov 09, 2000 at 09:17:09PM -0500, Barry wrote:
> > End Conclusion: Red Hat 7.0 is not a decent environment for building an
> > LFS implementation (or any software, for that matter)...
> RH7 _cannot_ be used for a development system, imho
> If a distrobution cannot even compile the latest stable kernel, latest
> stable gcc, etc...

Unsubscribe: send email to lfs-apps-request at
and put unsubscribe in the subject header of the message

More information about the blfs-support mailing list