Bug 407573 – ImportError: No module named portage.const from gcc-config while bootstrapping

• Status: RESOLVED FIXED
• Product: Gentoo/Alt

[Description Jeremy Olexa (darkside) (RETIRED) 2012-03-09 18:29:21 UTC]

Created attachment 304743 [details]
popt-1.16-r1 build.log

* QA Notice: Package triggers severe warnings which indicate that it
 *            will almost certainly crash on 64bit architectures.
 * 
 * Function `textdomain' implicitly converted to pointer at poptint.c:62
 * Function `bind_textdomain_codeset' implicitly converted to pointer at poptint.c:63

[Comment 1 Jeremy Olexa (darkside) (RETIRED) 2012-03-09 19:30:40 UTC]

ah-ha!

One thing causes another. During bootstrapping I saw this:

* gcc-config: Must be root

which is a python/portage issue:

ImportError: No module named portage.const

but I just ignored it and moved on. When I ran "gcc-config 1" THIS popt bug went away.

[Comment 2 Richard Yao (RETIRED) 2012-03-15 01:04:12 UTC]

This has been a pain for me on Mac OS X, although I have not figured out where the regression is yet. It happens on every new install I do on Mac OS X 10.6 and I just had a user using Mac OS X 10.7 in #gentoo-prefix run into it.

[Comment 3 Fabian Groffen 2012-03-24 09:12:22 UTC]

The problem occurs in gcc-config, right after the compiler has been emerged.  Python cannot find portage, which is because Python was installed in $EPREFIX/tmp, and Portage in $EPREFIX.  Setting PYTHONPATH appropriately fixes this problem.

[Comment 4 Fabian Groffen 2012-03-24 09:24:33 UTC]

Injecting PYTHONPATH now in our series of temporary profile hacks.