Andy McCarty <firstname.lastname@example.org> writes:
> OK I finally got everything to compile with threads
> on my FreeBSD box. But now "svn ci" hangs when run
> over ra_dav. It seems to work fine with ra_local.
> I am assuming this is an APR threads issue on FreeBSD.
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.
> setup is
> configured with --enable-threads --enable-dav --enable-so
I use one more flag than you, when configuring apache:
I discovered than on FreeBSD 4.X series, /dev/random blocks *hard* for
entropy, and apparently it only gets entropy from the keyboard. For
me, at least, Subversion was unable to generate random UUIDs unless I
was pressing the keyboard, so 'make check' wouldn't run at all, unless
I was typing. (I'm told that /dev/random and the entropy generator
are "all fixed" in FreeBSD 5.X.) /dev/urandom, however, doesn't block
for entropy, and is good enough for the UUID hashing function to work.
I wonder if you're experiencing something similar. How is the commit
"hanging"? What output do you see on the client? What do the apache
error/access logs say? What is the last bit of HTTP to traverse the
network (use etheral to capture)? Be more specific.
> Maybe this could be solved with an upgrade to FreeBSD 4.8?
> If APR_HAS_THREADS is required should it be checked for at
It's not required for svn, so svn's configure doesn't check for it.
> Not that it would solve my problem but it is very frustrating to get
> to the last file to compile, swigutil_py.c, to find out it won't
> compile with the configured APR.
The *swig* bindings, however, *do* require thread support. They're
not technically part of the svn "core". And I believe Sander(?)
recently added a compile-time check to them. If APR_HAS_THREADS is
undefined, then 'make swig-py' will simply bomb out with an
appropriate error message.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Jun 21 22:04:42 2003