[Cced to bug-hurd and hurd-devel.]
Hello!
For one part, this is essentally a repetition of
http://lists.gnu.org/archive/html/hurd-devel/2006-04/msg2.html;
everything in there still applies. For the other part, new issues are to
be worked on, see below.
On Sat, Aug 26, 2006 at 12:49:45AM
glibc 2.4 is completely unusable for GNU/Hurd at the moment,
Not true. It might be true for Debian GNU/Hurd though.
Also, a GCC 4.1-build glibc doesn't work correctly: it already
fails during the building process, as soon as the newly created
libc.so is being used (might also be
On Tue, Sep 05, 2006 at 11:05:12AM +0200, Alfred M. Szmidt wrote:
glibc 2.4 is completely unusable for GNU/Hurd at the moment,
Not true. It might be true for Debian GNU/Hurd though.
Wrong. It's also true for the glibc as it is in upstream's cvs
repository. Period. If you have patches
As I said, these patches will become avaiable with time. But as such,
both GCC and GLIBC work fine on GNU; you are of course free to inisist
on otherwise if that makes you happy.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Alfred M. Szmidt, le Tue 05 Sep 2006 11:57:08 +0200, a écrit :
As I said, these patches will become avaiable with time. But as such,
both GCC and GLIBC work fine on GNU; you are of course free to inisist
on otherwise if that makes you happy.
By as such, do you mean upstream glibc 2.4 release
As I said, these patches will become avaiable with time. But as
such, both GCC and GLIBC work fine on GNU; you are of course free
to inisist on otherwise if that makes you happy.
By as such, do you mean upstream glibc 2.4 release and gcc 4.1,
or your patched versions?
That is
Alfred M. Szmidt, le Tue 05 Sep 2006 12:44:12 +0200, a écrit :
As I said, these patches will become avaiable with time. But as
such, both GCC and GLIBC work fine on GNU; you are of course free
to inisist on otherwise if that makes you happy.
By as such, do you mean upstream
glibc hasn't worked out of the box for atleast a year since
malloc/memusage.c uses __thread without #if's.
Ok so glibc 2.4 as such doesn't work (that was the original
question).
glibc since 2.3 hasn't worked out of the box, either CVS or otherwise.
Nor will the malloc/memusage.c
On Sun, Aug 27, 2006 at 02:25:18PM -0400, Carlos O'Donell wrote:
On 8/27/06, Aurelien Jarno [EMAIL PROTECTED] wrote:
What are exactly the serious bugs currently with the NPTL version?
If I knew I would fix them. As Jeff says, there are serious testsuite
failures. We are debugging them as
On 8/29/06, Aurelien Jarno [EMAIL PROTECTED] wrote:
Ok I see. I actually asked that, because the testsuite was still running
when I sent my mail. Now it is finished, and I have see the errors in
the testsuite :( Thanks a lot for you hard work on the hppa glibc.
I think there are a handful of
Hi Carlos!
Carlos O'Donell a écrit :
Aurelian,
If you have any problems with hppa or need any help, please feel free
to email me directly or CC me on any problems. I'm the hppa libc-ports
maintainer, and I am actively working on TLS + NPTL support for hppa.
I am happy with TLS + Linuxthreads
On Sun, Aug 27, 2006 at 03:04:34PM +0200, Aurelien Jarno wrote:
What are exactly the serious bugs currently with the NPTL version?
There are 157 test errors in the glibc testsuite, including things like
mutexes. =)
gdb also hangs as soon as you try to debug a threaded program.
Tks,
Jeff
On 8/27/06, Aurelien Jarno [EMAIL PROTECTED] wrote:
What are exactly the serious bugs currently with the NPTL version?
If I knew I would fix them. As Jeff says, there are serious testsuite
failures. We are debugging them as fast as possible given the
volunteer nature of our effort.
Given the
On 8/25/06, Aurelien Jarno [EMAIL PROTECTED] wrote:
If we count the glibc in experimental all the architectures but the
following have TLS support:
- hppa
It has TLS support in upstream binutils, in gcc 4.1, and there are
patches available for glibc, they seems to work. Some people are
Hi m68k and hurd porters,
Thread Local Storage (TLS) support has been added to the toolchain
(binutils, gcc, glibc) some times ago. Currently about half of the
architectures have full TLS support (ie binutils + gcc + glibc).
If we count the glibc in experimental all the architectures but the
15 matches
Mail list logo
