People who have 'nptl' set will not be delighted to find they suddenly have linuxthreads libs on their system. Especially if the system has never had and therefore does not need linuxthreads. Please rename the flag to "linuxthreads-too" and change its function accordingly, so that people can safely emerge world without being hit by this ... "feature" ...
i have the ebuild beep furiously with a nice long warning about this. and technically the 'expected' behavior is exactly what it does now, as this is what most other nptl-using dists do. the behavior is hard-coded into glibc itself to check /lib/tls/ first and use the nptl libs there if they exist and LD_ASSUME_KERNEL isnt set to <2.6.0.
Beep eh? I never heard that, I don't have CONFIG_INPUT_PCSPKR in my kernel :-P "Expected" behaviour, AFAIC is what it was when I set my useflags... And finally: I think this is a step backwards, after all why have linuxthreads when you've compiled everything against nptl already? But, frankly, I could care less now that I _do_ have nptlonly in my useflags (and other people hopefully _will_ hear the beep ...)
