[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

FreeBSD and threads was Re: compile 0.24.2 errors

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2003-06-22 03:26:50 CEST

--On Saturday, June 21, 2003 3:02 PM -0500 Ben Collins-Sussman
<sussman@collab.net> wrote:

> Not at all. I've been building apache/subversion almost every day on
> FreeBSD for the last three years. I started at FreeBSD 4.2, and I
> have gradually "built world" through every release, and now I'm
> running 4.8. And I've always configured just like you, with
> --enable-threads forced for apache/apr/apu. Never had a problem.

Apache httpd's threaded MPMs (i.e. worker) do not even serve pages correctly
on FreeBSD. This is due to a number of problems residing in the core of
libc_r pertaining to network code. The APR developers have decided that
FreeBSD's threading code is not stable enough to be turned on by default.

To the best of our knowledge, we've isolated it to problems in the pthread
condition variables used with libc_r. We've heard reports from some FreeBSD
kernel developers that some later versions of FreeBSD (i.e. next major release
after 5) might have a rewritten libc_r that may address some of these problems.

>From the reports we've heard, FreeBSD 4.8 and 5.x are still broken and can not
serve pages. But, I've heard rumors that the 'right' people in FreeBSD land
are aware that libc_r is just broken and strongly discourage its use.

If Subversion uses any APR thread-level locking code (which I don't think it
does), don't expect it to work on FreeBSD if libc_r is linked in. -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 22 03:27:52 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.