Suse9.1 AMD64 build work-around

Hi!
When I am building subversion on suse 9.1,
I get errors from libtool at make install.

The error messages look like this:

cd subversion/libsvn_subr && /bin/sh /tmp/subversion-1.1.3/libtool --silent --mode=link gcc -g -O2 -g -O2 -pthread -DNEON_ZLIB -DNEON_SSL -rpath /usr/lib -o libsvn_subr-1.la auth.lo cmdline.lo config.lo config_auth.lo config_file.lo config_win.lo date.lo error.lo hash.lo io.lo md5.lo opt.lo path.lo pool.lo quoprint.lo sorts.lo stream.lo subst.lo svn_base64.lo svn_string.lo target.lo time.lo utf.lo utf_validate.lo validate.lo version.lo xml.lo /tmp/subversion-1.1.3/apr-util/libaprutil-0.la -lexpat /tmp/subversion-1.1.3/apr/libapr-0.la -lrt -lm -lcrypt -lnsl -lpthread -ldl
/usr/lib/libexpat.so: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make: *** [subversion/libsvn_subr/libsvn_subr-1.la] Error 1

This was discussed a lot on suse lists, see e.g.
http://lists.suse.com/archive/suse-amd64/2004-Oct/0412.html

The root cause (it seems) is that libtools is hard-coded to look for
libraries in /usr/lib, /lib etc, while the 64-bit libraries are actually in
/lib64, /usr/lib64 and such.

Here's a crude work-around that I use to make it pass, in the hope
that its useful to someone.
Not recommended for mainline, of course.

I expect the proper fix is to select the right directory dynamically,
probably based on gcc output.
Or, build with -m32 if supported which uses the libraries from /lib.

I think -rpath parameter which puts libraries under prefix/lib
has to be fixed, since the libraries are 64 bit and so shall be
going to under prefix/lib64

I could look into it more if someone's interested.

Hope this helps someone,
MST

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org