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

Re: HELP: Compiles one libsvn_* but not others.

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2002-06-19 02:15:55 CEST

On 19 Jun 2002, Philip Martin wrote:

> David Summers <david@summersoft.fay.ar.us> writes:
>
> > gcc -shared compose_delta.lo compose_editors.lo default_editor.lo diff.lo
> > diff_file.lo svndiff.lo text_delta.lo vdelta.lo xml_output.lo xml_parse.lo
> > -Wl,--rpath -Wl,/usr/local/apache2/lib -L/usr/local/apache2/lib -lcrypt
> > -ldl -L/usr/lib -lsvn_subr-1 -laprutil -lgdbm -ldb-4.0 -lexpat -lapr -lm
> > -lcrypt -lnsl -ldl -Wl,-soname -Wl,libsvn_delta-1.so.0 -o
> > .libs/libsvn_delta-1.so.0.0.0
> > /usr/bin/ld: cannot find -lsvn_subr-1
> > collect2: ld returned 1 exit status
> > libtool: install: error: relink `libsvn_delta-1.la' with the above command
> > before installing it
> > libtool: install: warning: remember to run `libtool --finish /usr/lib'
> > cd subversion/libsvn_ra_dav ; /bin/sh
> > /home/david/rpms/build/subversion-0.13.0/libtool --mode=install
> > /home/david/rpms/build/subversion-0.13.0/ac-helpers/install-sh -c
> > libsvn_ra_dav-1.la /home/david/rpms/tmp/subversion-0.13
> >
> > It sounds like the link commands are not getting the -L directory
> > correctly when the link happens so that it can't find the -lsvn_subr-1
> > can't locate the file correctly.
>
> When I link libsvn_delta the link command used is
>
> cd subversion/libsvn_delta && /bin/sh /home/pm/sw/subversion/obj/libtool --silent --mode=link gcc -DLINUX=2 -D_REENTRANT -DAPR_POOL_DEBUG=1 -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -g -Wall -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -DSVN_DEBUG -pthread -DNEON_ZLIB -I../svn/subversion/include -I. -I/usr/local/apache2/include -I/usr/local/apache2/include -I/usr/local/db4/include -I/usr/local/neon-0.21.2/include/neon -I/usr/local/db4/include -lcrypt -ldl -pthread -L/usr/local/db4/lib -rpath /usr/local/subversion/lib -o libsvn_delta-1.la compose_delta.lo compose_editors.lo default_editor.lo diff.lo diff_file.lo svndiff.lo text_delta.lo vdelta.lo xml_output.lo xml_parse.lo ../../subversion/libsvn_subr/libsvn_subr-1.la /usr/local/apache2/lib/libaprutil.la -ldb -lexpat /usr/local/apache2/lib/libapr.la -lm -lcrypt -lnsl -ldl
>
> which becomes
>
> gcc -shared compose_delta.lo compose_editors.lo default_editor.lo diff.lo diff_file.lo svndiff.lo text_delta.lo vdelta.lo xml_output.lo xml_parse.lo -Wl,--rpath -Wl,/home/pm/sw/subversion/obj/subversion/libsvn_subr/.libs -Wl,--rpath -Wl,/usr/local/apache2/lib -Wl,--rpath -Wl,/usr/local/subversion/lib -Wl,--rpath -Wl,/usr/local/apache2/lib -L/usr/lib -L/usr/local/apache2/lib -L/usr/local/db4/lib ../../subversion/libsvn_subr/.libs/libsvn_subr-1.so /usr/local/apache2/lib/libaprutil.so -ldb /usr/lib/libexpat.so /usr/local/apache2/lib/libapr.so -lm -lcrypt -lnsl -ldl -Wl,-soname -Wl,libsvn_delta-1.so.0 -o .libs/libsvn_delta-1.so.0.0.0
>
> It uses full paths to the libraries, so there is no need for -L directories.

That's what I would expect. I have no clue why mine is not doing that (it
didn't do that back on rev 1869) but it is completely reproducable as
of today (today is the first time I've been able to get APACHE to compile
for weeks). RPM starts from a clean slate every time (which is one reason
I really like it) so I don't think it has anything to do with a previous
install.

Any clues, pointers, suggestions appreciated.

  Thanks!

-- 
David Wayne Summers          "Linux: Because reboots are for upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 19 02:16:25 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.