On Wed, May 16, 2001 at 10:33:19AM -0500, email@example.com wrote:
> Kevin Pilch-Bisson <firstname.lastname@example.org> writes:
> > Just went to get a copy of M2 built, and noticed that I can't build the
> > client since LIBSVN_CLIENT_DEPS is not being set properly. All the fs
> > based dirs are being built, but not linked into the client. I don't
> > really have time to track it down right now, but if anyone else sees
> > something similar and can find it that would be great.
> My best guess is that perhaps you tried to build with shared
> libraries, or Berkeley wasn't found (but since the FS stuff reportedly
> built, I'm leaning toward the former). This from configure.in:
> dnl decide whether we want to link against the RA libraries
> if test "$enable_shared" = "no"; then
> AC_DEFINE(SVN_LIBSVN_CLIENT_LINKS_RA_DAV, 1,
> [Defined if libsvn_client should link against libsvn_ra_dav])
> LIBSVN_CLIENT_DEPS="$SVN_LIBSVN_RA_DAV_LIBS $SVN_NEON_LIBS"
> if test "$svn_lib_berkeley_db" = "yes"; then
> AC_DEFINE(SVN_LIBSVN_CLIENT_LINKS_RA_LOCAL, 1,
> [Defined if libsvn_client should link against libsvn_ra_local])
> $SVN_LIBSVN_RA_LOCAL_LIBS $SVN_LIBSVN_REPOS_LIBS $SVN_LIBSVN_FS_LIBS"
> Notice that the LIBSVN_CLIENT_DEPS macro is only created with
> $enable_shared set to "no".
> Should there be a LIBSVN_CLIENT_DEPS macro when $enable_shared is
> "yes"? I have no idea.
Good point, perhaps I should have explained the symptom, not the
suspected problem. The problem I am experiencing is that I can't link
the client because of missing symbols in libsvn_test, that refer to the
BTW I am building with shared libs.
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
Received on Sat Oct 21 14:36:30 2006
- application/pgp-signature attachment: stored