Bug#314289: to fix problem, reenable POSIX_THREADS (patch included)

2005-07-22 Thread Colin Watson
On Thu, Jul 21, 2005 at 08:57:49PM -0700, Jonathan Walther wrote: Disabling POSIX_THREADS was the problem. Here is a patch that reenables them (which will reopen other, less important bugs). Sorry, I'm not going to re-enable POSIX threads across the board; upstream are vehemently opposed to it

Bug#314289: to fix problem, reenable POSIX_THREADS (patch included)

2005-07-22 Thread Jonathan Walther
On Fri, Jul 22, 2005 at 11:00:41AM +0100, Colin Watson wrote: On Thu, Jul 21, 2005 at 08:57:49PM -0700, Jonathan Walther wrote: Disabling POSIX_THREADS was the problem. Here is a patch that reenables them (which will reopen other, less important bugs). Sorry, I'm not going to re-enable POSIX

Bug#314289: to fix problem, reenable POSIX_THREADS (patch included)

2005-07-22 Thread Jonathan Walther
On Fri, Jul 22, 2005 at 11:00:41AM +0100, Colin Watson wrote: On Thu, Jul 21, 2005 at 08:57:49PM -0700, Jonathan Walther wrote: Disabling POSIX_THREADS was the problem. Here is a patch that reenables them (which will reopen other, less important bugs). Sorry, I'm not going to re-enable POSIX

Bug#314289: to fix problem, reenable POSIX_THREADS (patch included)

2005-07-21 Thread Jonathan Walther
Tags: patch Disabling POSIX_THREADS was the problem. Here is a patch that reenables them (which will reopen other, less important bugs). A wiser head than mine will have to find out what differs between the threaded and non-threaded versions which causes this logging in problem. Since the