Summary: | dev-libs/nettle-3.4 Failed Running autoconf while bootstrapping Gentoo Prefix | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sammy Pfeiffer <sammypfeiffer> |
Component: | Current packages | Assignee: | Gentoo Prefix <prefix> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | kentnl |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sammy Pfeiffer
2018-11-26 07:41:25 UTC
(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 |