On 02 Jul 2001 11:19:09 -0500, Ben Collins-Sussman wrote:
>
> A friend of ours has discovered a compatibility problem between
> the latest libtool (1.4) and our build system.
>
> I was able to reproduce the problem myself. Here's what I did:
>
> * virgin RedHat 7.0 system
> * built & installed db3.2.9 and libtool 1.4
> * checked out subversion, apr, neon.
> * ./autogen && ./configure --enable-maintainer-mode --disable-shared
>
> When I run `make`, I get errors linking the svn binary:
> (snip)
> Our friend theorizes that the new libtool is somehow confused by our
> non-recursive make system. I don't know enough to diagnose. Anyone
> have a definitive analysis of the problem?
I'm the "friend".
This isn't the main problem. I'm attaching a patch containing my
efforts to get things to work w/ libtool 1.4 (which GNOME requires now,
among other things), which works around this.
The problem is that, during installs, when libtool needs to relink
libraries, it descends into the subdirectories and doesn't come back out
before trying to finish the install. Thus all of the relative pathnames
generated are wrong, and the install fails.
(This recursive descent isn't a problem normally, because the whole
autofoo tool-chain does recusive makes.)
One solution might be to make all install-related pathnames in the
generated makefile absolute paths. Which is kind of gross, but might be
necessary if you want to be able to assume that you are always operating
from the top-level directory.
-JT
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:32 2006