Fabian Groffen <mailto:firstname.lastname@example.org> wrote:
> On 02-04-2008 15:22:27 +0200, Duft Markus wrote:
>>> Feels like quite ancient to me, yes, but IIRC, portage.const should
>>> exist there too. Does 'import portage' work with your
>>> (bootstrapped) python? I think it works for noone during
>>> bootstrapping actually, unless python (from the tree) is emerged
>>> before reinstalling portage. I think my bootstrap docs at least for
>>> Mac OS X and Solaris (the only two that are possibly correct by the
>>> way) pull in python before portage reemerges itself (step 1.10 in
>>> the Solaris bootstrap) hence it works there. Maybe that's not an
>>> option for you, then we have to make a workaround.
>> I now tried to emerge python as first package, before portage. This
>> results in the same, since i have problems setting the PATH right.
>> The portage i use to bootstrap the prefix comes from
>> prefix-launcher, and (as all portage's do) insists on setting the
>> PATH to some known value (which doesn't include the dirs of the
>> to-bootstrap prefix, and hence misses the just installed python, but
>> rather gets the python 2.4 from prefix-launcher.
> a) muck with DEFAULT_PATH
> b) configure your bootstrap-portage differently (--default-path= or
> something) to include the right path before your prefix-launcher path
Used a) since i'm messing with environment anyway in the bootstrap
script, and i don't know what eprefix i will bootstrap at compile time,
so b) isn't possible.
Now the right python is found, but i have another problem: there is no
rpath hardcoded in python, so it doesn't find python2.5.so...... Need to
mess a little more with the environment
Cheers, and thanks, Markus
> Fabian Groffen
> Gentoo on a different level
email@example.com mailing list