Yeah they tried to update gcc a bit too fast. There's nothing wrong with
trying to offer the greatest version to the public, but they really should
have been more careful with a crucial tool like gcc. The solution could have
been to make a trick like debian's pentium-builder package. You export a
value telling which version of gcc you which to use and a wrapper script
redirect to the appropriate gcc.
Redhat got to be more careful in the future. It's really not a bad distro.
It's just that they have a big share of the linux market and, so far, they
hadn't made any great mistake. This situation is like Intel's pentium bug.
It really surprised, though when you think about it now, it wasn't such a
big deal :). In this case, Redhat is begining to solve this problem. Yeah
this was a long mistake!! So maybe you shouldn't call this 'glibc fiasco'
but rather a Bug (with a great B)... or, in debian notation, a critical bug!
BTW, I am in favor of a patched general kernel source on the CD. It would
really come in handy.
Coronya
On Mon, 9 Apr 2001, yan seiner wrote:
> Michael L Torrie wrote:
> >
> > On Sun, 8 Apr 2001, yan seiner wrote:
> >
>
> > What glibc fiasco are you talking about and how does it relate to the
> > kernel?
>
> RH 7 came out with a broken glibc and a non-standard compiler. The
> glibc was quickly patched (though it still remains broken for some
> international support) and everyone uses kgcc instead of RH's gcc.
>
> The generic kernel won't even compile on a RH system unless you use
> kgcc.
>
> --Yan
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
>
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
