Too late. Face it, if we are going to rebuild with a NPTL glibc and gcc 3.4,
we may not release sarge this year, at least not earlier than sarge+1 aka etch
would be released, so what do we gain with this ?
4.0 is still not ready to be used by anything but gcc hackers imho :)
now. but
Too late. Face it, if we are going to rebuild with a NPTL glibc and gcc 3.4,
we may not release sarge this year, at least not earlier than sarge+1 aka etch
would be released, so what do we gain with this ?
4.0 is still not ready to be used by anything but gcc hackers imho :)
now. but
On Thu, Jan 20, 2005 at 10:24:15AM +1100, Benjamin Herrenschmidt wrote:
Too late. Face it, if we are going to rebuild with a NPTL glibc and gcc 3.4,
we may not release sarge this year, at least not earlier than sarge+1 aka
etch
would be released, so what do we gain with this ?
I've been waiting ages for decent threads on PowerPC.
There's a glibc bug about it, with a way-too-low
priority. What gives?
If this has something to do with a Debian release,
well, just don't release PowerPC in that case.
It's not ready if it still uses the horrid old
pre-NPTL threads.
BTW,
On Tue, Jan 18, 2005 at 09:08:16AM -0500, Albert Cahalan wrote:
I've been waiting ages for decent threads on PowerPC.
We need to get debian/sarge out of the way, and then we can finally start
upgrading the glibc again. I am no glibc maintainer, but that is what i am
told. Sorry that the long
On Tue, 2005-01-18 at 18:09 +0100, Sven Luther wrote:
Don't be stupid, only a few people really need NPTL stuff, and you can always
follow testing/unstable once sarge is released.
This is a bogus argument actually :) It translates basically that only
a few people need more performant, more
On Tue, 2005-01-18 at 19:45, Benjamin Herrenschmidt wrote:
On Tue, 2005-01-18 at 18:09 +0100, Sven Luther wrote:
Don't be stupid, only a few people really need NPTL stuff, and you can
always
follow testing/unstable once sarge is released.
This is a bogus argument actually :) It
On Tue, 2005-01-18 at 19:43 -0500, Albert Cahalan wrote:
I'd be happy to run my code through the latest gcc if it were
available through the regular Debian package mechanism.
Be happy:
daenzer apt-cache policy gcc-4.0
gcc-4.0:
Installed: (none)
Candidate: 4.0-0pre4
Version Table:
Not even for potential bug reporters? Will a kernel boot
if compiled with gcc 4?
Well, it seems that on ppc64 at least, it sometimes does ... but
building glibc isn't quite good yet as of last night CVS... however, if
you are familiar with gcc hacking/reporting, I suppose you should go on,
but
9 matches
Mail list logo
