On Wed, 28 Mar 2001, Greg Stein wrote:
> > make[1]: Entering directory
> > `/usr/local/project/build/subversion/subversion/client'
> > /bin/sh ../../libtool --mode=link gcc -pthread -g
> > -Wall -o svn main.o status ...
> > ...
> > gcc: /usr/local/project/build/subversion/neon/src/.libs/.libs/libneon.a:
> > No such
> > file or directory
> > gcc:
> > /usr/local/project/build/subversion/subversion/libsvn_fs/.libs/.libs/libsvn
> > _fs.a: No such file or directory
> >
> >
> >
> > I got rid of the --quiet argument to libtool, it seems
> > that somewhere along the way, libtool adds a second .libs
> > dir to the relative path it is looking up.
> >
> > ../../neon/src/libneon.la -> /usr/local/project/build/subversion/neon/src/.libs/.libs/libneon.a
> >
> > This one has me stumped. Anyone have any ideas what might
> > have changed to cause this?
>
> There was a recent change to libsvn_ra_{dav,local}/Makefile.am to deal with
> cross-linking between shared libs. It's a hack cuz libtool is dumb, but I
> haven't found an alternative yet. Maybe this is causing your problem?
>
> Cheers,
> -g
It might be. I poked around a bit. It seems that some subdirs work
while others do not (libsvn_ra_dav good, libsvn_subr bad).
In libsvn_subr/Makefile.am, there is a sed that changes
the contents of libsvn_subr.la but only when --disable-shared
is passed to configure (which is how I build).
## copy files into Apache for static-linking
if IS_STATIC_APACHE
APLIB = libsvn_subr
## create a .la file with no shared library names (eg. force static lib
usage)
$(APLIB).la-a: $(APLIB).la
sed "/library_names/s/'.*'/''/" $< > $@
This has got to be it, but I am not really sure what
to do about it. I know that libtool is really dumb with
respect to mixing static and shared libs (and it is
even worse under Windows). Would an upgrade to a newer
version of libtool fix this? Autoconf 2.49 is almost
out, perhaps it would be a good time to upgrade
autoconf, automake, and libtool. That is kind of killing
a bug with a tank, but libtool problems have a way
of making you feel powerless. If libtool is not a
perfect example of why the test harness should not
be written with /bin/sh scripts, I don't know what
is.
Mo DeJong
Red Hat Inc
Received on Sat Oct 21 14:36:26 2006