On Wed, Mar 28, 2001 at 06:23:43PM -0000, email@example.com wrote:
> User: sussman
> Date: 01/03/28 10:23:43
> Modified: notes dav_setup.txt
> Add extra FreeBSD note.
> Revision Changes Path
> 1.4 +4 -1 subversion/notes/dav_setup.txt
> Index: dav_setup.txt
> RCS file: /cvs/subversion/notes/dav_setup.txt,v
> retrieving revision 1.3
> retrieving revision 1.4
> diff -u -r1.3 -r1.4
> --- dav_setup.txt 2001/03/28 01:13:03 1.3
> +++ dav_setup.txt 2001/03/28 18:23:43 1.4
> @@ -30,7 +30,10 @@
> The fourth arg says to use the "prefork" style of operation.
> NOTE: The fourth arg is needed for FreeBSD systems (broken
> threads), but should be left out for other platforms (which
> - will cause Apache to default to a threaded model of operation)
> + will cause Apache to default to a threaded model of
> + operation). Also note that "libmm.so" is needed for the
> + prefork option; if you're running FreeBSD, you may have to
> + build it out of /usr/ports.
MM is included within APR. In fact, APR's copy even has a few changes to it.
To "install" APR, you'd do something like the following:
$ cd apr/.libs
$ cp libapr.* /usr/local/lib
$ cd ../shmem/unix/mm/.libs
$ cp libmm.* /usr/local/lib
We don't happen to use shared memory, but advocating the use of a different
libmm could cause version skew somewhere.
And yes: we could end up picking up somebody's libmm anyways; we'll resolve
that separately with APR, but we should not advocate the skew right now.
[ in fact, APR is considering the removal of MM, so we may be safe in the
long run; we can wait and see ]
Lastly, the thing about libmm above is a misdirection. libmm is need for the
*client* ... not for Apache. Apache builds/links APR (and, thus, MM) as a
big-ass static link. It won't ever refer to libmm.so.
The client does, however, so the client needs libmm.so installed (if you're
building the client shared).
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:26 2006