Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 220589 - dev-scheme/guile-1.8.4-r1 - libtool 2.2.4 makes config fail
Summary: dev-scheme/guile-1.8.4-r1 - libtool 2.2.4 makes config fail
Status: RESOLVED DUPLICATE of bug 212723
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Marijn Schouten (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-06 13:48 UTC by M. Edward Borasky
Modified: 2008-05-06 20:15 UTC (History)
2 users (show)

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


Attachments
emerge --info from my system (info,4.81 KB, text/plain)
2008-05-06 13:49 UTC, M. Edward Borasky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description M. Edward Borasky 2008-05-06 13:48:24 UTC
libtool 2.2.4 showed up in the tree recently (5 May 2008 according to the ChangeLog). I did a revdep-rebuild, and it needed to rebuild guile--1.8.4-r1. However, the emerge of guile failed in the config step:

 # emerge -v guile

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] dev-scheme/guile-1.8.4-r1  USE="deprecated networking nls regex threads -debug -debug-freelist -debug-malloc -discouraged -elisp" 0 kB 

Total: 1 package (1 reinstall), Size of downloads: 0 kB

>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) dev-scheme/guile-1.8.4-r1 to /
 * guile-1.8.4.tar.gz RMD160 SHA1 SHA256 size ;-) ...                     [ ok ]
 * checking ebuild checksums ;-) ...                                      [ ok ]
 * checking auxfile checksums ;-) ...                                     [ ok ]
 * checking miscfile checksums ;-) ...                                    [ ok ]
 * checking guile-1.8.4.tar.gz ;-) ...                                    [ ok ]
>>> Unpacking source...
>>> Unpacking guile-1.8.4.tar.gz to /var/tmp/portage/dev-scheme/guile-1.8.4-r1/work
tar: guile-1.8.4/guile-readline/ltmain.sh: implausibly old time stamp 1969-12-31 16:00:00
tar: guile-1.8.4/build-aux/config.sub: implausibly old time stamp 1969-12-31 16:00:00
tar: guile-1.8.4/build-aux/config.guess: implausibly old time stamp 1969-12-31 16:00:00
tar: guile-1.8.4/build-aux/ltmain.sh: implausibly old time stamp 1969-12-31 16:00:00
 * Applying gcc-4.3.patch ...                                             [ ok ]
 * Running eautoreconf in '/var/tmp/portage/dev-scheme/guile-1.8.4-r1/work/guile-1.8.4' ...
 * Running aclocal -I guile-config ...                                    [ ok ]
 * Running libtoolize --copy --force --automake ...                       [ !! ]

 * Failed Running libtoolize !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/dev-scheme/guile-1.8.4-r1/temp/libtoolize-22169.out

 * 
 * ERROR: dev-scheme/guile-1.8.4-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 2911:  Called eautoreconf
 *             environment, line  971:  Called _elibtoolize '--copy' '--force'
 *             environment, line  293:  Called autotools_run_tool 'libtoolize' '--copy' '--force' '--automake'
 *             environment, line  438:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 *  The die message:
 *   Failed Running libtoolize !
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-scheme/guile-1.8.4-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-scheme/guile-1.8.4-r1/temp/environment'.
 * 

 * Messages for package dev-scheme/guile-1.8.4-r1:

 * Failed Running libtoolize !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/dev-scheme/guile-1.8.4-r1/temp/libtoolize-22169.out
 * 
 * ERROR: dev-scheme/guile-1.8.4-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 2911:  Called eautoreconf
 *             environment, line  971:  Called _elibtoolize '--copy' '--force'
 *             environment, line  293:  Called autotools_run_tool 'libtoolize' '--copy' '--force' '--automake'
 *             environment, line  438:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 *  The die message:
 *   Failed Running libtoolize !
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-scheme/guile-1.8.4-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-scheme/guile-1.8.4-r1/temp/environment'.
 * 

Dropping back to libtool 1.5.26 fixed this. Note: the attached "emerge --info" is with the *old* 1.5.26 libtool, but everything else should be the same.
Comment 1 M. Edward Borasky 2008-05-06 13:49:09 UTC
Created attachment 152117 [details]
emerge --info from my system
Comment 2 Devin Heckman 2008-05-06 19:03:43 UTC
Same problem. Output of libtoolize log file:

terrio rex ~ $ cat /var/tmp/portage/dev-scheme/guile-1.8.4-r1/temp/libtoolize-25043.out
***** libtoolize *****
***** libtoolize --copy --force --automake

libtoolize: AC_CONFIG_MACRO_DIR([m4]) conflicts with ACLOCAL_AMFLAGS=-I guile-config.

Comment 3 Marijn Schouten (RETIRED) gentoo-dev 2008-05-06 20:15:23 UTC

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