Philip Martin wrote:
> Julian Foad <julianfoad_at_btopenworld.com> writes:
>
> > Any ideas how to fix the build system to not get confused by older
> > installed libraries existing at the path where it is configured to
> > install to?
>
> It's an old bug, and hard to solve on all the platforms libtool
> supports.
>
> Does Ubuntu use Debian's patch for reducing libtool dependencies? If
> so then using a pristine upstream libtool might work. There is some
> history here:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291641
> and
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320698
>
> My own technique is to configure with --prefix to a non-existant
> location for my day-to-day development. When I decide to install a
> particular revision I reconfigure and rebuild with a proper prefix,
> moving the old libraries out of prefix/lib if necessary.
So it sounds like if we were to make the build system effectively
require (or even automatically perform) a "make uninstall" before
"make", that would solve it. That's not a good solution in general
because it's useful to be able to build before losing the current
install, on systems where that works, but it sounds like it would fix
the problem on systems like mine. Even a pre-make check that reported
"WARNING: You have Subversion libraries already installed in the
installation directory. This is known to cause incorrect linking on some
systems." would help.
- Julian
Received on 2010-01-22 16:22:36 CET