Your message dated Thu, 27 Sep 2018 19:03:53 +0200
with message-id <[email protected]>
and subject line Re: libtool: message about ACLOCAL_AMFLAGS
has caused the Debian Bug report #783227,
regarding libtool: message about ACLOCAL_AMFLAGS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
783227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783227
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libtool
Version: 2.4.2-1.11
Severity: normal
Tags: upstream
Forwarded: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20416
After removing a ACLOCAL_AMFLAGS line in Makefile.am of some software,
I get:
[...]
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
[...]
See the last line, about ACLOCAL_AMFLAGS.
However /usr/share/doc/automake/NEWS.gz says:
- The ACLOCAL_AMFLAGS special make variable will be fully deprecated in
Automake 2.0: it will raise warnings in the "obsolete" category (but
still no hard error of course, for compatibilities with the many, many
packages that still relies on that variable). You are advised to
start relying on the new Automake support for AC_CONFIG_MACRO_DIRS
instead (which was introduced in Automake 1.13).
meaning that ACLOCAL_AMFLAGS should no longer be used and
AC_CONFIG_MACRO_DIRS should be used instead, which is currently done
and taken into account, as seen above.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages libtool depends on:
ii autotools-dev 20140911.1
ii clang-3.4 [c-compiler] 1:3.4.2-13
ii clang-3.5 [c-compiler] 1:3.5-10
ii clang-3.6 [c-compiler] 1:3.6-2
ii cpp 4:4.9.2-2
ii file 1:5.22+15-2
ii gcc [c-compiler] 4:4.9.2-2
ii gcc-4.4 [c-compiler] 4.4.7-8
ii gcc-4.5 [c-compiler] 4.5.4-1
ii gcc-4.6 [c-compiler] 4.6.4-7
ii gcc-4.7 [c-compiler] 4.7.4-3
ii gcc-4.8 [c-compiler] 4.8.4-1
ii gcc-4.9 [c-compiler] 4.9.2-10
ii libc6-dev [libc-dev] 2.19-18
ii tcc [c-compiler] 0.9.27~git20140923.9d7fb33-3
Versions of packages libtool recommends:
ii libltdl-dev 2.4.2-1.11
Versions of packages libtool suggests:
ii autoconf 2.69-8
ii automake [automaken] 1:1.14.1-4
pn gcj-jdk <none>
ii gfortran 4:4.9.2-2
ii gfortran-4.7 [fortran95-compiler] 4.7.4-3
ii gfortran-4.8 [fortran95-compiler] 4.8.4-1
ii gfortran-4.9 [fortran95-compiler] 4.9.2-10
ii libtool-doc 2.4.2-1.11
-- no debconf information
--- End Message ---
--- Begin Message ---
Closing since I can no longer reproduce the issue (either the bug
was fixed or this was due to some old configuration). When I try
to reproduce it, I get the correct message (see upstream bug).
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
