libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool 1.5.6 still not supporting make distcheck


From: Ralf Wildenhues
Subject: Re: libtool 1.5.6 still not supporting make distcheck
Date: Mon, 15 Nov 2004 16:20:05 +0100
User-agent: Mutt/1.4.1i

* Sean Dague wrote on Thu, Nov 11, 2004 at 09:45:40PM CET:
> The issue I reported a couple weeks ago is still there.  We have now tracked
> down based on a number of versions of libtool to figure out what works and
> what doesn't.
> 
> libtool 1.4.x - all versions work that we've tried
> libtool 1.5.2 - works
> libtool 1.5.6 - doesn't work
> libtool 1.5.10 - doesn't work
> 
> The end of the logs are included at the end of this email (on libtool 1.5.6):

First: Your build is not VPATH clean, because you are doing a lot of
symlinking by hand in several Makefile.am's.  First, you should be using
$(LN_S) together with AC_PROG_LN_S for symlinks, second you should link
to $(srcdir)/relpath/$@ instead, third you should probably instead just
be using AC_CONFIG_LINKS and be happy that you don't have to care about
this yourself.  All explained in Autoconf docs.

Apart from these changes, `make distuninstallcheck' is the first part of
`make distcheck' to complain, and it complains about some files which
`make uninstall' misses to remove.  This is with the HEAD branch as well
as branch-1-5 of libtool.

So, can you try either the patch from
http://lists.gnu.org/archive/html/bug-libtool/2004-10/msg00170.html
and possibly branch-2-0 from CVS?  Please tell us your findings.

> What is most interesting is that the
> /home/sdague/tmp/am-dc-21838//home/sdague/openhpi/openhpi-1.9.3/ directory
> doesn't exist at all on my system.  That seems to be created very late in
> the make distcheck processing, but why it isn't there I'm not sure.

I /think/ this has nothing to do with your problem (though I cannot be
sure, as I haven't understood what went wrong), and is fine because
`make distcheck' is attempting a DESTDIR install.

BTW, you did not mention your system at all, neither whether you are
doing a VPATH build or not.  All of this would have been helpful (still
is if the problem remains unsolved), also whether or not an installed
version of your package exists on your system or not.

Regards,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]