[Top][All Lists]

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

Re: Automake 1.7.2b uploaded (beta for 1.7.3)

From: Robert Boehne
Subject: Re: Automake 1.7.2b uploaded (beta for 1.7.3)
Date: Thu, 13 Feb 2003 09:28:42 -0600


I have a problem with the beta, after bootstrapping a
fresh checkout of Libtool with Autoconf 2.57 and Automake
1.7.2b, I get a make distcheck error.  Apparently the
distcheck fails because files are left over in the
insallation directory after "make uninstall" is run.
Below are the offending files
install-sh  missing  mkinstalldirs

Is this a bug or misuse?

Robert Boehne

ERROR: files left after uninstall:
make[1]: *** [distuninstallcheck] Error 1
make[1]: Leaving directory `/net/libtool/libtool-1.4e/_build'
make: *** [distcheck] Error 2
address@hidden libtool]$ ls -R /net/libtool/libtool-1.4e/_inst
bin  include  info  lib  share





aclocal  libtool


install-sh  missing  mkinstalldirs

Alexandre Duret-Lutz wrote:
> Hi people!
> Here is a snapshot of the 1.7.x branch of Automake.
> This should be reasonably close to what 1.7.3 will be.
> Please test it and report any problem you have to <address@hidden>.
> I hope we can release 1.7.3 by the middle of next week.
>   There is a known bug with VPATH handling of Texinfo and Lex rules
>   which isn't fixed here.  This affects all 1.7.x versions for Texinfo
>   rules.  I think older versions will also fails on Lex rules but I
>   haven't verified.  This is triggered during VPATH builds with (at
>   least) Tru64 make, FreeBSD (current) make, and OpenBSD (3.2) make.
>   In short, these make implementations will *not* perform a
>   VPATH search for dependencies which appear as targets in Makefiles.
>   As far as BSD make is concerned this seems to be a recent change in
>   its behavior, as I believe it worked fine in the past.
>   Fixing this requires too much changes for the 1.7.x branch.
>   The following failures in the test suite can denote this bug:
>     lex3.test, txinfo3.test, txinfo13.test, txinfo16.test, txinfo18.test
>   Please report these failures anyway, with your system's version,
>   so we know more precisely where this happens.
> Here is a list of changes since 1.7.1.  Those that worry me the more
> are the changes to elisp compilation, and the changes to depcomp.  If
> you can test these, by all means please do!
> Bugs fixed in 1.7.2b:
> * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
> * Query distutils for `pythondir' and `pythonexecdir', instead of
>   using an hardcoded path.  This should allow builds on 64-bit
>   distributions that usually use lib64/ instead of lib/.
> * AM_PATH_PYTHON will also search for python2.3.
> * elisp files are now built all at once instead of one by one. Besides
>   incurring a speed-up, this is required to support interdependent elisp 
> files.
> * Support for DJGPP:
>   - `make distcheck' will now work in `_inst/' and `_build' instead
>     of `=inst/' and `=build/'
>   - use `_dirstamp' when the file-system doesn't support `.dirstamp'
>   - more changes that affect only the Automake package (not its output)
> * Fix some incompatibilities with upcoming perl-5.10.
> * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
> * depcomp fixes:
>   - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
>     is troublesome with gcc and Solaris compilers. (PR/385)
>   - makedepend mode: work with Libtool. (PR/385 too)
>   - support for ICC.
> * better support for unusual gettext setups, such as multiple po/ directories
>   (PR/381):
>   - Flag missing po/ and intl/ directories as warnings, not errors.
>   - Disable these warnings if po/ does not exist.
> * Noteworthy manual updates:
>   - New FAQ chapter.
>   - Document how AC_CONFIG_AUX_DIR interacts with missing files.
>     (Debian Bug #39542)
>   - Document `AM_YFLAGS = -d'.  (PR/382)
> --
> Alexandre Duret-Lutz

reply via email to

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