On Tue, Sep 26, 2006 at 12:57:50AM -0500, Manoj Srivastava wrote: > > On Mon, Sep 25, 2006 at 01:20:16AM -0700, Steve Langasek wrote:
> >> Could you check if changing "-lpthread" to "-pthread" works? > > Yes, it works. Thanks. > > It also works with e2fsprogs, which was the original reason for the > > change in libselinux (#388375). > > Thus I'm reassigning. > > Manoj, can you change: > > Libs.private: -lthread > > to > > Libs.private: -pthread > > in libselinux.pc. > Sure. Mind you, man gcc has this to say: > -pthread > Add support for multithreading using the POSIX threads library. > This option sets flags for both the preprocessor and linker. It > does not affect the thread safety of object code produced by the > compiler or that of libraries supplied with it. These are HP-UX > specific flags. > Is the gcc documentation incorrect? Yes; it's something of an artifact of how gcc's documentation groups options by processor target. If you look at the sections closely you'll see that gcc simply doesn't document -pthread *at all* for most hardware targets, even though it's the official way to get pthread support on all of Debian's release architectures[1]. :/ -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ [1] I say "official" here, because there is a corner case on mips/mipsel where this doesn't work as expected: if you create a shared lib which uses libpthread, and you link it using -pthread *without* -lpthread, you will get undefined symbol errors. This is a toolchain bug, and I'm not sure static linking a shared lib against libselinux is likely enough to happen to bother dealing with the corner case in the .pc file. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
