Problem with aclocal

[pamplemousse]

Hello
I'm trying to install on my macbook c2d. I use the doc
http://www.gentoo.org/proj/en/gentoo-al ... tstrap.xml
to do this. At the time I must emerge -e system, I get a problem with emerging libtools and aclocal. After looking around in this forum, I decided to remerge coreutil like this:

emerge coreutils -eav


I still have the problem of aclocal like this:

Code: Select all

>>> Emerging (20 of 20) sys-apps/coreutils-6.4 to /
 * coreutils-6.4-patches-1.0.tar.bz2 MD5 ;-) ...                          [ ok ]
 * coreutils-6.4-patches-1.0.tar.bz2 RMD160 ;-) ...                       [ ok ]
 * coreutils-6.4-patches-1.0.tar.bz2 SHA1 ;-) ...                         [ ok ]
 * coreutils-6.4-patches-1.0.tar.bz2 SHA256 ;-) ...                       [ ok ]
 * coreutils-6.4-patches-1.0.tar.bz2 size ;-) ...                         [ ok ]
 * coreutils-6.4.tar.bz2 MD5 ;-) ...                                      [ ok ]
 * coreutils-6.4.tar.bz2 RMD160 ;-) ...                                   [ ok ]
 * coreutils-6.4.tar.bz2 SHA1 ;-) ...                                     [ ok ]
 * coreutils-6.4.tar.bz2 SHA256 ;-) ...                                   [ ok ]
 * coreutils-6.4.tar.bz2 size ;-) ...                                     [ ok ]
 * checking ebuild checksums ;-) ...                                      [ ok ]
 * checking auxfile checksums ;-) ...                                     [ ok ]
 * checking miscfile checksums ;-) ...                                    [ ok ]
 * checking coreutils-6.4.tar.bz2 ;-) ...                                 [ ok ]
 * checking coreutils-6.4-patches-1.0.tar.bz2 ;-) ...                     [ ok ]
>>> Unpacking source...
>>> Unpacking coreutils-6.4.tar.bz2 to /Library/Gentoo/var/tmp/portage/sys-apps/coreutils-6.4/work
>>> Unpacking coreutils-6.4-patches-1.0.tar.bz2 to /Library/Gentoo/var/tmp/portage/sys-apps/coreutils-6.4/work
 * Applying various patches (bugfixes/updates) ...
 *   000_all_coreutils-i18n.patch ...                                     [ ok ]
 *   003_all_coreutils-gentoo-uname.patch ...                             [ ok ]
 *   009_all_coreutils-tests.patch ...                                    [ ok ]
 *   030_all_coreutils-more-dir-colors.patch ...                          [ ok ]
 *   150_all_coreutils-l10n-updates.patch ...                             [ ok ]
 * Done with patching
 * Running eautoreconf in '/Library/Gentoo/var/tmp/portage/sys-apps/coreutils-6.4/work/coreutils-6.4' ...
 * Requested autoconf 2.5
 * Using autoconf (GNU Autoconf) 2.60
 * Using autoheader (GNU Autoconf) 2.60
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory
 * Requested automake latest: 1.6
 * Using 
 * Using 
 * Running aclocal -I m4 ...
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: line 1799:  4881 Trace/BPT trap          $@ >>${STDERR_TARGET%/*}/$1-${STDERR_TARGET##*/} 2>&1             [ !! ]

 * Failed Running aclocal !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /Library/Gentoo/var/tmp/portage/sys-apps/coreutils-6.4/temp/aclocal-4482.out


!!! ERROR: sys-apps/coreutils-6.4 failed.
Call stack:
  , line :   Called die

!!! Failed Running aclocal !
!!! If you need support, post the topmost build error, and the call stack if relevant.

Is there a way to fix this?
Bye.

[Valkura]

I by no means have any idea what I'm doing, but

Code: Select all

/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: /Library/Gentoo/usr/lib/portage/bin/portageq: /Library/Gentoo/tmp/usr/bin/python: bad interpreter: No such file or directory

and

Code: Select all

 * Running aclocal -I m4 ...
/Library/Gentoo/usr/lib/portage/bin/ebuild.sh: line 1799:  4881 Trace/BPT trap          $@ >>${STDERR_TARGET%/*}/$1-${STDERR_TARGET##*/} 2>&1             [ !! ]

Look most important.

Since nobody here is posting anything, I'll give it a shot:

Google yielded me similar errors:

When configuring x11-base/xgl-0.0.1_pre20061108 I got an error that said
Failed Running aclocal !
Apparently, 0.0.1_pre20061108 uses automake version 1.10, so I had to put
>sys-devel/automake-1.9.6
in /etc/portage/package.keywords to unmask automake-1.10. I re-emerged automake and it compiled fine after that.

at http://gentoo-wiki.com/Talk:HOWTO_XGL

Also, look at this link to see if anything there is helpful.

Good luck!

EDIT - there might be some helpful stuff here as well, since assuming my short term memory isn't crap you are also working toward prefixed portage on OS X

[somekool]

>>> Emerging (6 of 71) media-sound/alsa-utils-1.0.14_rc2-r3 to /
* alsa-utils-1.0.14rc2.tar.bz2 RMD160 ... [ ok ]
* alsa-utils-1.0.14rc2.tar.bz2 SHA1 ... [ ok ]
* alsa-utils-1.0.14rc2.tar.bz2 SHA256 ... [ ok ]
* alsa-utils-1.0.14rc2.tar.bz2 size ... [ ok ]
* checking ebuild checksums ... [ ok ]
* checking auxfile checksums ... [ ok ]
* checking miscfile checksums ... [ ok ]
* checking alsa-utils-1.0.14rc2.tar.bz2 ... [ ok ]
>>> Unpacking source...
>>> Unpacking alsa-utils-1.0.14rc2.tar.bz2 to /var/tmp/portage/media-sound/alsa-utils-1.0.14_rc2-r3/work
* Applying alsa-utils-1.0.11_rc2-nls.patch ... [ ok ]
* Applying alsa-utils-1.0.11_rc5-alsaconf-redirect.patch ... [ ok ]
* Applying alsa-utils-1.0.14_rc2-seq.patch ... [ ok ]
* Running eautoreconf in '/var/tmp/portage/media-sound/alsa-utils-1.0.14_rc2-r3/work/alsa-utils-1.0.14rc2' ...
* Running aclocal -I m4 ... [ !! ]

* Failed Running aclocal !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/media-sound/alsa-utils-1.0.14_rc2-r3/temp/aclocal-19821.out


!!! ERROR: media-sound/alsa-utils-1.0.14_rc2-r3 failed.
Call stack:
ebuild.sh, line 1615: Called dyn_unpack
ebuild.sh, line 752: Called qa_call 'src_unpack'
ebuild.sh, line 44: Called src_unpack
alsa-utils-1.0.14_rc2-r3.ebuild, line 47: Called eautoreconf
autotools.eclass, line 93: Called eaclocal
autotools.eclass, line 130: Called autotools_run_tool 'aclocal' '-I' 'm4'
autotools.eclass, line 218: Called die

!!! Failed Running aclocal !
!!! 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/media-sound/alsa-utils-1.0.14_rc2-r3/temp/build.log'.

somekool@krypton ~ $

It's the third package I'm getting a similar error in the last few days.

[grobian]

I think you messed up the order. It looks like things are referring still to the $EPREFIX/tmp location, while they should have been replaced. Follow the steps from the bootstrap document carefully, and report at which step you get stuck on gentoo-alt@lists.gentoo.org please.

[somekool]

I am not quite sure to understand what you are telling me..... what order did I messed up?

I am just doing .... emerge alsa-utils and it crash like that.

I think the cause is because I've downgraded autoconf to 2.59 in order to fix a problem with ruby. now automake is not happy.

[grobian]

portageq points to the temporary python installation, which should have not been the case. Due to that, everything can go wrong. After emerging python, portage should be reemerged *before* removing the tempdir.