Hello, I was bootstrapping Gentoo Prefix with the bootstrap-prefix.sh script, on the official Docker image stage3-x86 (so I'm trying to take advantage of the existing Gentoo to make the process faster). To reach this point I did docker pull gentoo/stage3-x86 docker run -it gentoo/stage3-x86 /bin/bash wget https://gist.githubusercontent.com/awesomebytes/e6c8da6e1e339014f27b506c47b4fbb2/raw/bbe3f3b8ed8ec299123d5d5afd59a0b48955243e/bootstrap-prefix.sh chmod +x bootstrap-prefix.sh # This bootstrap-prefix.sh includes the workaround on the first comment of this bug report https://bugs.gentoo.org/668940 HOST_GENTOO_EROOT=/tmp/gentoo setarch i686 ./bootstrap-prefix.sh # Here I answer the interactive questions with EPREFIX being /tmp/gentoo # And allowing to use the pre-existing Gentoo to fasten up the process (in theory) I reached the point in stage3 where nettle failed configuring: >>> Emerging (23 of 66) dev-libs/nettle-3.4::gentoo * nettle-3.4.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking nettle-3.4.tar.gz to /tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/work >>> Source unpacked in /tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/work >>> Preparing source in /tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/work/nettle-3.4 ... * Running eautoreconf in '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/work/nettle-3.4' ... * Running autoconf --force ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/temp/autoconf.out * ERROR: dev-libs/nettle-3.4::gentoo failed (prepare phase): * Failed Running autoconf ! * * Call stack: * ebuild.sh, line 124: Called src_prepare * environment, line 1854: Called eautoreconf * environment, line 819: Called eautoconf '--force' * environment, line 732: Called autotools_run_tool '--at-m4flags' 'autoconf' '--force' * environment, line 546: Called die * The specific snippet of code: * die "Failed Running $1 !"; * * If you need support, post the output of `emerge --info '=dev-libs/nettle-3.4::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-libs/nettle-3.4::gentoo'`. * The complete build log is located at '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/temp/build.log'. * The ebuild environment file is located at '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/temp/environment'. * Working directory: '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/work/nettle-3.4' * S: '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/work/nettle-3.4' >>> Failed to emerge dev-libs/nettle-3.4, Log file: >>> '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/temp/build.log' * Messages for package dev-libs/nettle-3.4: * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/temp/autoconf.out * ERROR: dev-libs/nettle-3.4::gentoo failed (prepare phase): * Failed Running autoconf ! * * Call stack: * ebuild.sh, line 124: Called src_prepare * environment, line 1854: Called eautoreconf * environment, line 819: Called eautoconf '--force' * environment, line 732: Called autotools_run_tool '--at-m4flags' 'autoconf' '--force' * environment, line 546: Called die * The specific snippet of code: * die "Failed Running $1 !"; * * If you need support, post the output of `emerge --info '=dev-libs/nettle-3.4::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-libs/nettle-3.4::gentoo'`. * The complete build log is located at '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/temp/build.log'. * The ebuild environment file is located at '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/temp/environment'. * Working directory: '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/work/nettle-3.4' * S: '/tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/work/nettle-3.4' * GNU info directory index is up-to-date. * IMPORTANT: config file '/tmp/gentoo/etc/hosts' needs updating. * See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS * sections of the emerge man page to learn how to update config files. Note that as I'm bootstrapping Gentoo Prefix... I don't know how to execute emerge --info '=dev-libs/nettle-3.4::gentoo' Making sure I'm using the bootstrapped environment and not the actual Gentoo environment.
(In reply to Sammy Pfeiffer from comment #0) > * Include in your bugreport the contents of: > * > * /tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/temp/autoconf.out Where is it?
(In reply to Jeroen Roovers from comment #1) > (In reply to Sammy Pfeiffer from comment #0) > > > * Include in your bugreport the contents of: > > * > > * /tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/temp/autoconf.out > > > Where is it? Luckily I still had the Docker spinning in the machine, the contents of that file are: ***** autoconf ***** ***** PWD: /tmp/gentoo/var/tmp/portage/dev-libs/nettle-3.4/work/nettle-3.4 ***** autoconf --force ac-wrapper: Unable to locate any usuable version of autoconf. I tried these versions: 2.69:2.5 2.68:2.5 9999:2.5 2.99:2.5 2.98:2.5 2.97:2.5 2.96:2.5 2.95:2.5 2.94:2.5 2.93:2.5 2.92:2.5 2.91:2.5 2.90:2.5 2.89:2.5 2.88:2.5 2.87:2.5 2.86:2.5 2.85:2.5 2.84:2.5 2.83:2.5 2.82:2.5 2.81:2.5 2.80:2.5 2.79:2.5 2.78:2.5 2.77:2.5 2.76:2.5 2.75:2.5 2.74:2.5 2.73:2.5 2.72:2.5 2.71:2.5 2.70:2.5 2.69:2.5 2.68:2.5 2.67:2.5 2.66:2.5 2.65:2.5 2.64:2.5 2.63:2.5 2.62:2.5 2.61:2.5 2.60:2.5 2.59:2.5 2.13:2.1 With a base name of '/tmp/gentoo/usr/bin/autoconf'.
@crypt/alonbl: I'm removing you as this is a bootstrap problem. autoconf is not yet installed, hence autoreconf fails. I don't think this is not something you have to consider. nettle needs autoconf, and autoconf isn't ready yet at that stage. Question is, what pulls in nettle? Is it wget?
(In reply to Fabian Groffen from comment #3) > @crypt/alonbl: I'm removing you as this is a bootstrap problem. autoconf is > not yet installed, hence autoreconf fails. I don't think this is not > something you have to consider. > > nettle needs autoconf, and autoconf isn't ready yet at that stage. Question > is, what pulls in nettle? Is it wget? nettle will get pulled these days if you have no USE flags customized and try to emerge a recent portage. As this is a dependency of: # app-crypt/gnupg[ssl] # via app-portage/gemato[gpg] # via sys-apps/portage[rsync-verify] I don't *think* bootstrap builds portage with that on, but I could be wrong.
this is fixed on today's state of the tree