Two questions first, then the background, the first question (mostly)
for Mr. Erenkrantz:
1. Is there really such a thing as jlibtool that fixes glibtool under
OS X, and where do I get it?
2. Does svn build against BerkeleyDB 4.1 yet, and if not, is the mutex
fix for 4.0, which Kevin Bond posted back in October, automatically
applied by anything yet?
I realize I'm probably one of the few people in the world who build the
svn server under Mac OS X, so thanks to all for your time and energy
helping me out.
As per people's advice (very helpful, actually, thanks) I blew away my
old svn, neon, apache, etc. and then the bootstrapping tarball for svn
built fine. I got svn checked out with it, got apache and neon and
Building svn now gives me the following error during make:
gcc: -install_name only allowed with -dynamiclib
make: *** [subversion/mod_dav_svn/mod_dav_svn.la] Error 1
Now, this sounded weirdly familiar, and in fact I seem to recall having
this problem building svn 0.14.3 and tweaking my glibtool a while back
to fix this (I thought I had made a note somewhere of what I did, but I
can't find it now). I'm using the following version of glibtool under
Mac OS X:
% glibtool --version
ltmain.sh (GNU libtool) 1.4.2 (1.922.2.53 2001/09/11 03:18:52)
And here's the line from glibtool that seems relevent:
archive_cmds="\$nonopt \$(test x\$module = xyes && echo -bundle || echo
-dynamiclib) \$allow_undefined_flag -o \$lib \$libobjs
\$deplibs\$linker_flags -install_name \$rpath/\$soname \$verstring"
On Tuesday, January 28, 2003, at 10:29 PM, Justin Erenkrantz wrote:
> --On Tuesday, January 28, 2003 11:14 AM -0700 Hamilton Link
> <firstname.lastname@example.org> wrote:
>> Question 1: are these warnings serious?
>> cc1: warning: changing search order for system directory
>> "/usr/local/include" cc1: warning: as it has already been
>> specified as a non-system directory
> Not really. But, it means you are explicitly including something from
> /usr/local/include/. That leads to #2.
>> Question 2: what does this error mean, and what might be the cause?
>> -L/usr/local/lib -lz -lexpat ld: Undefined symbols:
> As Sussman pointed out, you probably installed SVN in /usr/local. It's
> trying to link against the old libraries, not the newer one. You can't
> install SVN when you already have it installed. Your linker doesn't
> like that. Very few linkers do. -- justin
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Feb 14 21:03:19 2003