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 perf
Volker Armin Hemmann wrote:
try older binary only software.
I'll stick with stuff built fresh from sources, thanks ;-).
Zac
--
gentoo-user@gentoo.org mailing list
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 prob
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 be
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
t
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, yo
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
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
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 Lin
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 threa
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
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
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-high
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
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
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 3
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
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:
--- snip ---
/var/tmp/portage/glibc-2.3.5/work/build-default-i586-pc-linux-gnu-linuxthrea
ds/linuxthreads/libpthread_pic.a(pthread.os)(.text+0x1cd): In functi
18 matches
Mail list logo
