I've not found any problems with GLIB 2.2. Mandrake's cooker (8.0) now
uses it as well. So it's going to be standard pretty soon. 2.1 had some
important threading issues that 2.2. supposedly fixed. I ended up
replacing the compiler in rh 7 with GCC 2.95.1 (will try mandrake's rpms
for gcc 2.95.3 soon). With compatibility libraries for glibc 2.1 and the
older standard c++ library installed, I've had relatively few problems.
the normal gcc will build the kernel fine. I'll wait until GCC 3.0 is
officially released someday before I ever upgrade the compiler again.
Also, the majority of problems that gcc 2.96(snapshot) has are related to
ansi compliance. The compiler breaks old, non-compliant code. This is a
royal pain however. Also, the reason the kernel doesn't build under rh's
snapshot gcc is not because the compiler is broken, but because the kernel
is not ansi compliant because of workarounds for the older, broken, gcc's.
GCC has pretty much always been broken in many areas including template
handling and ansi compliance. GCC 3.0 will address these issues. When it
becomes widely available, the kernel source code will have to be changed
to compile under it.
Michael
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
