On Tuesday 17 May 2005 01:37, Grant wrote: > > > If I use -nptlonly instead of +, do I still risk incompatibilities? > > > > with ntplonly you WILL have problems. With 'nptl', you can say the apps > > which implementation to use. Great for broken/old apps with problems. BUT > > if you use ntplonly you can NOT go back, and if an app has a problem with > > nptl, you are out of luck. So, just remove ntplonly from your make.conf > > and everything will be fine. Since nptlonly should not be set by default, > > removing nptlonly should be as good as -nptlonly ;) > > How do you tell an app to use linuxthreads instead? What is the point > of +nptlonly? A more compact installation? > > - Grant
Matan Peled answered all this in his email to this thread: Matan Peled <[EMAIL PROTECTED]> wrote: Loki's Sim City 3000 Unlimited, for example, doesn't work with nptl. Some other binary apps too, perhaps. nptlonly makes the ebuild not build a non-nptl libc, which means you can't fall back on linux threads like so: LD_ASSUME_KERNEL=2.4.5 foo #### so, with nptl flag, you are building glibc basically two times, one with nptl, one with linuxthreads as fallback. If you set nptlonly, you will not have this fallback, and some apps, mostly games, will not work anymore. -- gentoo-user@gentoo.org mailing list
