Bug 527100 – bootstrap prefix fails on OS X because bash-4.1_p17 fails to compile (does not respect USE=-readline)

• Status: RESOLVED FIXED
• Product: Gentoo/Alt

[Description Guilherme Amadio 2014-10-27 16:33:43 UTC]

When bootstrapping a prefix on OS X Yosemite, bash-4.1_p17 fails to compile because the USE=-readline is not respected. See build log.

Reproducible: Always

[Comment 1 Guilherme Amadio 2014-10-27 16:35:01 UTC]

Created attachment 387564 [details]
Build log

[Comment 2 Guilherme Amadio 2014-10-27 17:17:21 UTC]

Since bash-4.1_p17 was older than what was bootstrapped before, I took a look and found out that it was being pulled by portage via:

RDEPEND="!build? ( >=sys-apps/sed-4.0.5
 || ( >=app-shells/bash-4.2_p37[readline] ( <app-shells/bash-4.2_p37 >=app-shells/bash-4.1 ) )

when trying to emerge sys-devel/gettext and net-misc/wget.

So I fixed this by recompiling bash with readline enabled right before emerging sys-devel/gettext and net-misc/wget during bootstrapping of stage3. That way the dependency no longer pulls bash-4.1_p17 without readline, which fails to compile.

[Comment 3 Fabian Groffen 2014-10-27 17:36:34 UTC]

Was this with a LATEST snapshot?  If not, please try that.  I didn't get this problem.

[Comment 4 Guilherme Amadio 2014-10-27 18:03:53 UTC]

Yes, this was with a latest snapshot from rsync8.bitzolder.nl (I ran emerge --sync by hand during bootstrap). I believe this is more of a problem with the bootstrap-prefix.sh script than bash or portage themselves. Maybe you used a different bootstrap script than me?

[Comment 5 Fabian Groffen 2014-10-27 18:18:22 UTC]

make sure you downloaded the latest version from rsync8.

[Comment 6 Guilherme Amadio 2014-10-27 18:30:49 UTC]

I will restart everything from scratch using rsync8. Up to what point did your bootstrapping process go?

[Comment 7 Fabian Groffen 2014-10-27 18:32:07 UTC]

python

[Comment 8 Guilherme Amadio 2014-10-27 20:50:37 UTC]

I started fresh using LATEST_TREE_YES=1 and hit this bug again.

[Comment 9 yegle 2014-11-02 16:32:27 UTC]

Same here, tried yesterday with LATEST_TREE_YES=1 and failed at this point.

Guilherme's workaround (emerge higher version of bash) works.

[Comment 10 Fabian Groffen 2014-11-02 20:49:47 UTC]

hmmmm, why do we need bash-4.1 again?

[Comment 11 Guilherme Amadio 2014-11-03 01:56:48 UTC]

We don't need bash-4.1, but because it is built during earlier stages with USE=-readline, the dependencies are such that when stage3 tries to emerge portage, it pulls the old version, which unfortunately doesn't compile because it doesn't respect the USE flags. So, instead, the workaround is to rebuild the same bash with USE=readline before emerging portage, so that emerge portage doesn't try to install the older version of bash as a dependency.

[Comment 12 Guilherme Amadio 2014-11-23 19:12:41 UTC]

Created attachment 390156 [details, diff]
This patch is a possible fix for this bug.

[Comment 13 Ruud Koolen (RETIRED) 2014-11-24 10:15:16 UTC]

Fixed in the new bootstrap script.