Ahoy... I have noticed that in the Sarge/Kernel 2.6 combo, glibc is not providing an archive of the NPTL libpthread.a for purposes of static linking, but it *does* provide a static LinuxThreads libpthread.a.
This leads to the puzzling scenario in which default dynamic linking picks up NPTL, but *no* statically linked app can make use of NPTL. (Aside, perhaps, from using dlopen!) Is there a known workaround / separate package / etc. that would provide this library? I can understand the fear of letting users build statically linked applications that will not be compatable with the majority of linux distros out there, but to effectively forbid any developer from doing so seems a tad heavy handed. (Obtaining sources and building my own NPTL libpthread.a involves building all of glibc as far as I can tell, and that's a daunting proposition.) Or... am I missing something incredibly obvious? -blunt jackson -:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
