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

Re: Linux build problem

From: Justin Erenkrantz <jerenkrantz_at_apache.org>
Date: 2002-06-13 11:51:42 CEST

On Wed, Jun 12, 2002 at 05:32:44PM -0700, Robert A Nesius wrote:
> The build error I'm currently stuck on:
> =+=+=+=+=+=+=+=+=+=+=+=+
> ------ completed all in neon
> cd subversion/libsvn_subr && /bin/sh /fs3/comp.apps_build.1/subversion/linux22/libtool --silent --mode=link /usr/bin/gcc -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -O2 -L/usr/intel/pkgs/zlib/1.1.3/lib -L/usr/intel/pkgs/openssl/0.9.6/lib -pthread -I../subversion-r2140/subversion/include -I. -I/fs3/comp.apps_build.1/subversion/linux22/apr/include -I/fs3/comp.apps_build.1/subversion/subversion-r2140/apr/include -I/fs3/comp.apps_build.1/subversion/linux22/apr-util/include -I/fs3/comp.apps_build.1/subversion/subversion-r2140/apr-util/include -I/fs3/comp.apps_build.1/subversion/subversion-r2140/neon/src -I/fs3/comp.apps_build.1/subversion/linux22/db/dist -rpath /fs34/a/rnesius/proj/subversion/lib -o libsvn_subr.la config.lo config_file.lo config_win.lo getdate.lo hash.lo io.lo path.lo quoprint.lo sorts.lo svn_base64.lo svn_error.lo svn_string.lo target.lo time.lo xml.lo /fs3/comp.apps_build.1/subversion/linux22/apr-util/libaprutil.la -lgdbm -ldb -lexpat /fs3
/comp.apps_build.1/subversion/linux22/apr/libapr.la -lm -lcrypt -lnsl -ldl
> libtool: link: cannot find the library `/fs3/comp.apps_build.1/subversion/linux22/apr-util/libaprutil.la'
> =+=+=+=+=+=+=+=+=+=+=+=+
> This is interesting. I cannot find libaprutil.la anywhere
> in my build area. Nor were there any error messages
> indicating that the build failed to create this object.
> I'm using the tarball from the webpage that was released
> a few days ago. (r2140)
> Any ideas, or info about where this library is
> supposed to come from?

Hmm. You should have a libaprutil.la file if apr-util was built
properly. What is in your apr-util directory? Is there anything
called libaprutil or something like that?

You could try building apr and apr-util first and then go build
SVN. Then, use --with-apr and --with-apr-util to point SVN at
your APR and APR-util locations. In fact, if you are planning on
building a SVN server with httpd-2.0 and mod_dav_svn, you get the
APR and APR-util libraries for 'free' - so you can configure
subversion with:

./configure \
--with-apr=/path/to/my/httpd-2.0/install \

That might help in case SVN's build system is doing something screwy.

> Other build oddities: When using gcc 3.0.2, I encountered
> an internal compiler error. gcc 2.96 (redhat's gcc)
> works fine so far.

I'd use gcc-3.1 as that is the latest official version.
I don't know what version RH officially supports.

> Although now that I think about it, I'm wondering if
> the lack of a -L<path_to_db_libs> may have fixed it.
> I wouldn't think that would necessary when using an
> explicit configure directive though.

You may need "-Wl,-rpath,<path_to_db_libs>" set in your LDFLAGS.

> Lastly, I'm a bit fuzzy on one build detail. Do I need
> to build my apache server first, then the subversion
> client, or does the order not matter. I wasn't 100%
> certain on that one.

If you are going to trying to build mod_dav_svn so you can have your
own SVN server, you must build and install httpd-2.0 first so that
SVN can build mod_dav_svn correctly.

> I'm also not certain if I am satisfying the libautoconf
> requirement. What's the best way to tell? (Just build
> the latest autoconf and make sure the build can see it?)

autogen.sh will ensure you have the right version. But, if
you use a snapshot from the website, you don't need to run
that. If you are using a development checkout (i.e. checked
out using SVN), you must run autogen.sh.

HTH. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 13 11:52:15 2002

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