Summary: | dev-libs/libmcrypt-2.5.8-r2 uses obsolete autoconf macro AM_CONFIG_HEADER | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tobias Klausmann (RETIRED) <klausman> |
Component: | [OLD] Library | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alonbl, axs, datty.wtb, jason.mours, rose |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 451744 |
Description
Tobias Klausmann (RETIRED)
2013-04-24 08:36:10 UTC
Similar failures occur in media-libs/gd (466996) media-libs/jbig2dec (466998), app-text/ghostscript-gpl and media-libs/libwmf (no bug reports yet) also fail. All with errors about obsolete macros in configure.ac! I'm reporting this here, since the problems seem related. Sorry if this is the worng place. (In reply to comment #1) > Similar failures occur in media-libs/gd (466996) media-libs/jbig2dec > (466998), app-text/ghostscript-gpl and media-libs/libwmf (no bug reports > yet) also fail. All with errors about obsolete macros in configure.ac! > > I'm reporting this here, since the problems seem related. Sorry if this is > the worng place. It's the right place in principle, but for new packages, a new bug should be opened and linked to (as blocking) bug 451744. Be sure to check whether it's a known bug, first. dev-libs/libmcrypt-2.5.8-r2 is failing on my end. Here is my aclocal.out ***** aclocal ***** ***** PWD: /var/tmp/portage/dev-libs/libmcrypt-2.5.8-r2/work/libmcrypt-2.5.8 ***** aclocal aclocal-1.13: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:16: error: 'AM_CONFIG_HEADER': this macro is obsolete. You should use the 'AC_CONFIG_HEADERS' macro instead. /usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from... configure.in:16: the top level autom4te-2.69: /usr/bin/m4 failed with exit status: 1 aclocal-1.13: error: echo failed with exit status: 1 I can also report failed aclocal with app-text/ghostscript-gpl-9.06. Not sure if this is pertinent; but not recorded in the build logs is emerge failing with an orphaned PID : /usr/lib64/portage/bin/isolated-functions.sh : line 215: wait: 'Failed Running aclocal !': not a pid or valid job spec & /usr/lib64/portage/bin/isolated-functions.sh : line 246: kill: (10632) - No such process Fixed in libmcrypt-2.5.8-r3 *** Bug 468632 has been marked as a duplicate of this bug. *** Not fixed. It still fails for AM_CONFIG_HEADER in libltdl/configure.in:
>>> Preparing source in /var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8 ...
* Applying libmcrypt-2.5.8-rotate-mask.patch ... [ ok ]
* Running eautoreconf in '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8' ...
* Running eautoreconf in '/var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8/libltdl' ...
* Running libtoolize --install --copy --force --automake ... [ ok ]
* Running aclocal ...
* Running libtoolize --copy --force --automake ... [ ok ]
* Running aclocal ... [ !! ]
* Failed Running aclocal !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/temp/aclocal-1.out
***** aclocal *****
***** PWD: /var/tmp/portage/dev-libs/libmcrypt-2.5.8-r3/work/libmcrypt-2.5.8/libltdl
***** aclocal
aclocal-1.13: warning: autoconf input should be named 'configure.ac', not 'configure.in'
acinclude.m4:3740: warning: the serial number must appear before any macro definition
configure.in:25: error: 'AM_CONFIG_HEADER': this macro is obsolete.
You should use the 'AC_CONFIG_HEADERS' macro instead.
/usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from...
configure.in:25: the top level
autom4te-2.69: /usr/bin/m4 failed with exit status: 1
aclocal-1.13: error: echo failed with exit status: 1
(In reply to comment #7) > Not fixed. It still fails for AM_CONFIG_HEADER in libltdl/configure.in: Strange... not happening for me... will fix. Thanks! *** Bug 467662 has been marked as a duplicate of this bug. *** *** Bug 468856 has been marked as a duplicate of this bug. *** |