Re: Linking against libpth and libpthread

2002-01-27 Thread Andy Wingo
On Sun, 27 Jan 2002, Ralf S. Engelschall wrote: > Does anybody know what the problem with __errno_location in LinuxThreads > is? I looked into this last week and it goes like this: __errno_location() is a function that returns a pointer to errno from LinuxThreads' internal structure representing

Re: Linking against libpth and libpthread

2002-01-27 Thread Ralf S. Engelschall
In article <[EMAIL PROTECTED]> you wrote: > [This was previously a bug report involving -lpth and -lgc on Debian > GNU/Linux. I found out that the problem stems from -lgc dragging in > -lpthread.] > > This is a simple test to show that Pth and Pthreads can't run in the > same executable on my

Re: Linking against libpth and libpthread

2002-01-06 Thread David Schwartz
On 05 Jan 2002 21:42:51 -0600, Gordon Matzigkeit wrote: >This is a simple test to show that Pth and Pthreads can't run in the same >executable on my machine. Is there a good reason why this is so? >I would have thought that Pth would happily run in a single kernel thread. Look at the

Linking against libpth and libpthread

2002-01-06 Thread Gordon Matzigkeit
[This was previously a bug report involving -lpth and -lgc on Debian GNU/Linux. I found out that the problem stems from -lgc dragging in -lpthread.] This is a simple test to show that Pth and Pthreads can't run in the same executable on my machine. Is there a good reason why this is so? I would