View previous topic :: View next topic |
Author |
Message |
kilburna Tux's lil' helper
Joined: 20 Sep 2004 Posts: 107
|
Posted: Sun Apr 28, 2013 7:08 pm Post subject: tar fails to emerge with automake 1.12 |
|
|
Tar not compiling
>>> Emerging (1 of 5) app-arch/tar-1.26-r1
* tar-1.26.tar.bz2 SHA256 SHA512 WHIRLPOOL size ... [ ok ]
>>> Unpacking source...
>>> Unpacking tar-1.26.tar.bz2 to /var/tmp/portage/app-arch/tar-1.26-r1/work
>>> Source unpacked in /var/tmp/portage/app-arch/tar-1.26-r1/work
>>> Preparing source in /var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26 ...
* Applying tar-1.26-xattr.patch ... [ ok ]
* Applying tar-1.26-no-gets.patch ... [ ok ]
* Running eautoreconf in '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26' ...
* Running autopoint --force ... [ ok ]
* Running aclocal -I m4 ... [ ok ]
* Running autoconf ... [ ok ]
* ERROR: app-arch/tar-1.26-r1 failed (prepare phase):
* internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 3178: Called eautoreconf
* environment, line 921: Called eautoheader
* environment, line 843: Called _at_uses_autoheader
* environment, line 268: Called _at_uses_pkg 'AC_CONFIG_HEADERS' 'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER'
* environment, line 300: Called autotools_check_macro 'AC_CONFIG_HEADERS' 'AC_CONFIG_HEADER' 'AM_CONFIG_HEADERS' 'AM_CONFIG_HEADER'
* environment, line 596: Called die
* The specific snippet of code:
* has ${macro} ${ALL_AUTOTOOLS_MACROS[@]} || die "internal error: add ${macro} to ALL_AUTOTOOLS_MACROS";
*
* If you need support, post the output of `emerge --info '=app-arch/tar-1.26-r1'`,
* the complete build log and the output of `emerge -pqv '=app-arch/tar-1.26-r1'`.
/usr/lib64/portage/bin/isolated-functions.sh: line 215: wait: `internal error: add AC_CONFIG_HEADER to ALL_AUTOTOOLS_MACROS': not a pid or valid job spec
* The complete build log is located at '/var/tmp/portage/app-arch/tar-1.26-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-arch/tar-1.26-r1/temp/environment'.
* Working directory: '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26'
* S: '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26' |
|
Back to top |
|
|
mahdi1234 Guru
Joined: 19 Feb 2005 Posts: 559 Location: Being There
|
|
Back to top |
|
|
TomWij Retired Dev
Joined: 04 Jul 2012 Posts: 1553
|
|
Back to top |
|
|
kernelOfTruth Watchman
Joined: 20 Dec 2005 Posts: 6111 Location: Vienna, Austria; Germany; hello world :)
|
|
Back to top |
|
|
krenshala Tux's lil' helper
Joined: 28 Jan 2006 Posts: 85 Location: Austin TX, NorAm, Sol III
|
Posted: Mon Oct 14, 2013 3:55 am Post subject: |
|
|
I was updating today and ran into this problem just now. I tried this solution just to see and it didn't change anything. The autotools.eclass I had originally was 1.156. With 1.155 I get the error as displayed at the top of this thread, but with 1.156 I get the following:
Code: | >>> Emerging (1 of 1) app-arch/tar-1.26-r1
* tar-1.26.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking tar-1.26.tar.bz2 to /var/tmp/portage/app-arch/tar-1.26-r1/work
>>> Source unpacked in /var/tmp/portage/app-arch/tar-1.26-r1/work
>>> Preparing source in /var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26 ...
* Applying tar-1.26-xattr.patch ... [ ok ]
* Applying tar-1.26-no-gets.patch ... [ ok ]
* Running eautoreconf in '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26' ...
* Running autopoint --force ... [ !! ]
* Failed Running autopoint !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/app-arch/tar-1.26-r1/temp/autopoint.out
* ERROR: app-arch/tar-1.26-r1::gentoo failed (prepare phase):
* Failed Running autopoint !
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 3295: Called eautoreconf
* environment, line 910: Called autotools_run_tool '--at-missing' 'autopoint' '--force'
* environment, line 687: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
*
* If you need support, post the output of `emerge --info '=app-arch/tar-1.26-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=app-arch/tar-1.26-r1::gentoo'`.
/usr/lib64/portage/bin/isolated-functions.sh: line 188: wait: `Failed Running autopoint !': not a pid or valid job spec
* The complete build log is located at '/var/tmp/portage/app-arch/tar-1.26-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-arch/tar-1.26-r1/temp/environment'.
* Working directory: '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26'
* S: '/var/tmp/portage/app-arch/tar-1.26-r1/work/tar-1.26'
>>> Failed to emerge app-arch/tar-1.26-r1, Log file:
>>> '/var/tmp/portage/app-arch/tar-1.26-r1/temp/build.log' |
I get the same failure when attempting to update wget-1.14 so I'm assuming its the same root cause as the bug report from April. These are the only two packages left in @system for me to update. Should I add this to the (currently closed) bug report referenced above, or create a new one? _________________ krenshala
:wq |
|
Back to top |
|
|
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Mon Oct 14, 2013 8:47 am Post subject: |
|
|
krenshala, you assume too much.
The original log and the one, you've posted clearly fail at a different point.
Check the file referenced by your log for hints. |
|
Back to top |
|
|
krenshala Tux's lil' helper
Joined: 28 Jan 2006 Posts: 85 Location: Austin TX, NorAm, Sol III
|
Posted: Mon Oct 14, 2013 12:46 pm Post subject: |
|
|
The one for both tar and wget reads as follows:
Code: | kitsune ~ # cat /var/tmp/portage/net-misc/wget-1.14/temp/autopoint.out
***** autopoint *****
***** PWD: /var/tmp/portage/net-misc/wget-1.14/work/wget-1.14
***** autopoint --force
autopoint: *** cvs program not found
autopoint: *** Stop. |
There are differences between what I'm seeing and the OPs error, however, both appear (to me at least) to have something to do with eautoreconf. I could quite easily be wrong, of course.
edit: Apparently, I was wrong. Found this thread that shows the error i was getting and the fact that remerging gettext was the fix. Trying that now. I'll drop off this thread at this point to avoid cluttering it further. _________________ krenshala
:wq |
|
Back to top |
|
|
|