Re: [gentoo-user] Cannot emerge glibc
Volker Armin Hemmann wrote: On Sunday 17 July 2005 00:55, Zac Medico wrote: Volker Armin Hemmann wrote: but there is enough stuff out there, that does not work with ntpl. So recommending ntplonly is irresponsible. No problems here. I'd expect people to do their own research before making the switch. Plus, you can swap in a linuxthreads glibc at any time if need be, right? yeah, but problems are known. So there are good reasons NOT to use ntplonly or to advise to use it generally. And if you mean 'reemerge glibc' you are right, you can always 'swap' them around. What problems? bugs.gentoo.org only lists a few open bugs when I search for nptl, that even mention nptl, and the only apps mentioned are bittornado or skype. The bittornado one is more than a year old, while the skype one seems more like a artsd problem. No bugs are found when I search for nptlonly. I personally have been using nptlonly for 6 months on my P4, without incident. Are these problems only on non-x86 platforms? -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
On Sunday 17 July 2005 10:49, Richard Fish wrote: Volker Armin Hemmann wrote: On Sunday 17 July 2005 00:55, Zac Medico wrote: Volker Armin Hemmann wrote: but there is enough stuff out there, that does not work with ntpl. So recommending ntplonly is irresponsible. No problems here. I'd expect people to do their own research before making the switch. Plus, you can swap in a linuxthreads glibc at any time if need be, right? yeah, but problems are known. So there are good reasons NOT to use ntplonly or to advise to use it generally. And if you mean 'reemerge glibc' you are right, you can always 'swap' them around. What problems? bugs.gentoo.org only lists a few open bugs when I search for nptl, that even mention nptl, and the only apps mentioned are bittornado or skype. The bittornado one is more than a year old, while the skype one seems more like a artsd problem. No bugs are found when I search for nptlonly. I personally have been using nptlonly for 6 months on my P4, without incident. Are these problems only on non-x86 platforms? -Richard try older binary only software. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Zac Medico wrote: Linuxthreads are the *old* linux threading library and nplt is the *new* linux threading library. I've been using nptlonly for a couple months now with no noticeable problems. AFAICT it's a drop in replacement for linuxthreads and it supposed to give superior performance. I'd recommend it. I've set the nptl and nptlonly use variables in my make.conf. After 4 hours, the build completed successfully. /lib/libc.so.6 now reports Native POSIX Threads Library by Ulrich Drepper et al and everything seems to work fine. Cheers Alex -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Alexander Veit wrote: Hi, When I try to emerge -u world, the only package that's going to be updated is glibc. However the build fails with the following error: MAKEOPTS=-j3 -j3 causes many build problems for many packages that build internal libraries and then try to link against them. -j1 is much safer. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Richard Fish wrote: [...] MAKEOPTS=-j3 -j3 causes many build problems for many packages that build internal libraries and then try to link against them. -j1 is much safer. OK, now make runs with -j1. Unfortunately, on my machine, it takes a long long time for the first 3K files to be built... BTW is there a way to resume the build process at the point where the error occurred? emerge --resume does not resume in the middle of a broken build. -- Alex -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Alexander Veit wrote: Richard Fish wrote: [...] MAKEOPTS=-j3 -j3 causes many build problems for many packages that build internal libraries and then try to link against them. -j1 is much safer. OK, now make runs with -j1. Unfortunately, on my machine, it takes a long long time for the first 3K files to be built... BTW is there a way to resume the build process at the point where the error occurred? emerge --resume does not resume in the middle of a broken build. There are tons of ways to do this but here's what I would do: FEATURES=keepwork emerge --resume The drawback is that with FEATURES=keepwork portage will not clean up builds in PORTAGE_TMPDIR so you will have to do that yourself in order to reclaim disk space. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Zac Medico wrote: Alexander Veit wrote: Unfortunately, on my machine, it takes a long long time for the first 3K files to be built... BTW is there a way to resume the build process at the point where the error occurred? emerge --resume does not resume in the middle of a broken build. There are tons of ways to do this but here's what I would do: FEATURES=keepwork emerge --resume The drawback is that with FEATURES=keepwork portage will not clean up builds in PORTAGE_TMPDIR so you will have to do that yourself in order to reclaim disk space. Thank you for this hint, Zac. Sure I'll need it. After two hours of compiling glibc with -j1, it failed with the same error :-( -- Alex -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
On Saturday 16 July 2005 22:14, Alexander Veit wrote: Thank you for this hint, Zac. Sure I'll need it. After two hours of compiling glibc with -j1, it failed with the same error :-( Seems to be a known and not yet resolved problem on i586 hosts. http://forums.gentoo.org/viewtopic-t-329143-highlight-pthreadinitialize+res.html Regards Daniel -- Those who would give up essential liberty, to purchase a little temporary safety, deserve neither liberty nor safety. - Benjamin Franklin -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Daniel Heemann wrote: On Saturday 16 July 2005 22:14, Alexander Veit wrote: Thank you for this hint, Zac. Sure I'll need it. After two hours of compiling glibc with -j1, it failed with the same error :-( Seems to be a known and not yet resolved problem on i586 hosts. http://forums.gentoo.org/viewtopic-t-329143-highlight-pthreadinitialize+res.html Regards Daniel Yep, here's another forum thread and an open bug: http://forums.gentoo.org/viewtopic-t-343187-highlight-.html http://bugs.gentoo.org/show_bug.cgi?id=90236 I can tell you that it will work with i586 CHOST and USE=nptl nptlonly. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Daniel Heemann wrote: Seems to be a known and not yet resolved problem on i586 hosts. http://forums.gentoo.org/viewtopic-t-329143-highlight-pthreadi nitialize+res.html Daniel, thank your for this link. It will have saved me a lot of time... -- Alex -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Zac Medico wrote: Yep, here's another forum thread and an open bug: http://forums.gentoo.org/viewtopic-t-343187-highlight-.html http://bugs.gentoo.org/show_bug.cgi?id=90236 I can tell you that it will work with i586 CHOST and USE=nptl nptlonly. Hmm. I guess, on Linux Linux threads would be the appropriate threads. So I'll wait for this bug being fixed. Thank you Alex -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Alexander Veit wrote: Zac Medico wrote: Yep, here's another forum thread and an open bug: http://forums.gentoo.org/viewtopic-t-343187-highlight-.html http://bugs.gentoo.org/show_bug.cgi?id=90236 I can tell you that it will work with i586 CHOST and USE=nptl nptlonly. Hmm. I guess, on Linux Linux threads would be the appropriate threads. So I'll wait for this bug being fixed. Thank you Alex Linuxthreads are the *old* linux threading library and nplt is the *new* linux threading library. I've been using nptlonly for a couple months now with no noticeable problems. AFAICT it's a drop in replacement for linuxthreads and it supposed to give superior performance. I'd recommend it. Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
On Saturday 16 July 2005 23:58, Zac Medico wrote: Alexander Veit wrote: Zac Medico wrote: Yep, here's another forum thread and an open bug: http://forums.gentoo.org/viewtopic-t-343187-highlight-.html http://bugs.gentoo.org/show_bug.cgi?id=90236 I can tell you that it will work with i586 CHOST and USE=nptl nptlonly. Hmm. I guess, on Linux Linux threads would be the appropriate threads. So I'll wait for this bug being fixed. Thank you Alex Linuxthreads are the *old* linux threading library and nplt is the *new* linux threading library. I've been using nptlonly for a couple months now with no noticeable problems. AFAICT it's a drop in replacement for linuxthreads and it supposed to give superior performance. I'd recommend it. but there is enough stuff out there, that does not work with ntpl. So recommending ntplonly is irresponsible. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Volker Armin Hemmann wrote: but there is enough stuff out there, that does not work with ntpl. So recommending ntplonly is irresponsible. No problems here. I'd expect people to do their own research before making the switch. Plus, you can swap in a linuxthreads glibc at any time if need be, right? Zac -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
On Sunday 17 July 2005 00:55, Zac Medico wrote: Volker Armin Hemmann wrote: but there is enough stuff out there, that does not work with ntpl. So recommending ntplonly is irresponsible. No problems here. I'd expect people to do their own research before making the switch. Plus, you can swap in a linuxthreads glibc at any time if need be, right? yeah, but problems are known. So there are good reasons NOT to use ntplonly or to advise to use it generally. And if you mean 'reemerge glibc' you are right, you can always 'swap' them around. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Cannot emerge glibc
Volker Armin Hemmann wrote: On Sunday 17 July 2005 00:55, Zac Medico wrote: Volker Armin Hemmann wrote: but there is enough stuff out there, that does not work with ntpl. So recommending ntplonly is irresponsible. No problems here. I'd expect people to do their own research before making the switch. Plus, you can swap in a linuxthreads glibc at any time if need be, right? yeah, but problems are known. So there are good reasons NOT to use ntplonly or to advise to use it generally. And if you mean 'reemerge glibc' you are right, you can always 'swap' them around. If you're like me then nptlonly works fine for everything you use. You know that if a hypothetical nptl problem should arise, you have a quick and simple recovery plan. I might not have switched if rollback wasn't so simple. Zac -- gentoo-user@gentoo.org mailing list
