Re: [Cooker] is there a problem with glibc 2.3.1 ?

[Per �yvind Karlsen]

Peter Ruskin wrote:

On Saturday 26 Oct 2002 15:43, Wesley J Landaker wrote:

On Saturday 26 October 2002 08:26 am, Pascal Terjan wrote:

Florent BERANGER wrote:

RedHat have it and C applications, as KDE, are faster, it's a
known thing.

Kde is c++ or am i wrong ?
And the fact that cooker kde is slow does not come from glibc...
look at the kde shipped in 9.0 it's really fast.

All GCC C++ programs linked to glibc as well as libstdc++. Not to
mention that most of the other libraries that KDE links to also
depend on glibc. With extremely few exceptions, *every* program on
your system uses glibc regardless of the language it's written in.

Not to say that upgrading glibc is going to necessarily have a
drastic effect on performance, but if you could only upgrade one
library and wanted to get the most bang for your buck, glibc would be
the one to pick. =)

To answer the question in the title, yes there are problems with glibc 2.3.1. It can break a lot of stuff already built against previous versions. Red Hat has used a workaround - not a fix. Gentoo has it in "unstable" (where it belongs).

I would advise against rushing into it.

Peter

this is unstable/devel/testing/whatever and things built against previous versions should be rebuilt, so was the case with gcc-3.1,3.2 and other major upgrades;)


--
Mvh Per �yvind Karlsen
Delonic Technology Group AS
Sysadmin, developer, greasemonkey
www.delonic.no - +47 41681061