Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 468856 - =dev-libs/libmcrypt-2.5.8-r2 - configure.in:16: error: 'AM_CONFIG_HEADER': this macro is obsolete.
Summary: =dev-libs/libmcrypt-2.5.8-r2 - configure.in:16: error: 'AM_CONFIG_HEADER': th...
Status: RESOLVED DUPLICATE of bug 467058
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Robin Johnson
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: automake-1.13
  Show dependency tree
 
Reported: 2013-05-07 11:11 UTC by Oliver Smith
Modified: 2013-05-07 21:22 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Emerge --info (info.txt,14.62 KB, text/plain)
2013-05-07 11:11 UTC, Oliver Smith
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Smith 2013-05-07 11:11:20 UTC
Created attachment 347594 [details]
Emerge --info

Package is failing running aclocal.

Output of 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

Making the following changes as suggested allows the package to build:

File : configure.in
   line:16 AC_CONFIG_HEADERS(config.h)
File : libltdl/configure.in
   line: 25 AC_CONFIG_HEADERS(config.h:config-h.in)

Apologies for not attaching a patch, I'm not sure how to make one. I have attached my emerge --info.

Thanks
Comment 1 Alon Bar-Lev (RETIRED) gentoo-dev 2013-05-07 21:22:52 UTC

*** This bug has been marked as a duplicate of bug 467058 ***