Tried to install Gentoo on an AMD Athlon 1200 system, with boot CD 2006.0 x86 minimal. Installed stage-3-i686-2006.0.tar.bz2, portage-latest.tar.bz2 as indicated in the gentoo handbook. After changeroot (handbook), I tried to perform env-update. !!! Failed to complete python imports. There are internal modules for !!! python and failure here indicates that you have a problem with python !!! itself and thus portage is not able to continue processing. !!! You mitght consider starting python with verbose flags to see what has !!! gone wrong. Here is the information we got for this exception: math range error python -v indicates no obvious error.
Tried to install Gentoo on an AMD Athlon 1200 system, with boot CD 2006.0 x86 minimal. Installed stage-3-i686-2006.0.tar.bz2, portage-latest.tar.bz2 as indicated in the gentoo handbook. After changeroot (handbook), I tried to perform env-update. !!! Failed to complete python imports. There are internal modules for !!! python and failure here indicates that you have a problem with python !!! itself and thus portage is not able to continue processing. !!! You mitght consider starting python with verbose flags to see what has !!! gone wrong. Here is the information we got for this exception: math range error python -v indicates no obvious error. ´modules math´ doesn't show an error
So you extracted the tarball and did the chroot, correct? I am unable to reproduce this using the same tarball. Are you sure that the tarball matches the digests? It sounds like you might have gotten a corrupted download or something. Also, the problem has nothing to do with the CD that you're on, as it is within the chroot, which means the stage tarball.
(In reply to comment #1) > So you extracted the tarball and did the chroot, correct? I am unable to > reproduce this using the same tarball. Are you sure that the tarball matches > the digests? It sounds like you might have gotten a corrupted download or > something. Also, the problem has nothing to do with the CD that you're on, as > it is within the chroot, which means the stage tarball. > Tried it also with older stage3-tarballs. But that had also no effect. P.S.: This is not my first gentoo installation. Successfully installed AMD64 and x86, that run as productive server systems. So I cannot understand, what might be wrong at that point. Might this be a hardware problem with the mathematic processor unit within the Athlon processor? I have no idea ...
Are you saying the older tarballs gave you the same error?
(In reply to comment #3) > Are you saying the older tarballs gave you the same error? > Yes. I tried stage3-x86-2006.0, stage3-i686-2006.0, stage3-i686-2005.1-r1, stage3-athlon-xp-2005.1. The last one might not be the right tarball for the processer type, but it showed the same error.
(In reply to comment #3) > Are you saying the older tarballs gave you the same error? > P.S.: Accidentally, I saw this error message also while booting with the livelinux-cd gentoo 2006.0 installer i686, as a boot messages, just before the kde comes up. The comes up while the video card is detected.
It would pretty much have to be either: #1 - some crazy kernel incompatibility #2 - hardware Try running mirrorselect from the CD, without pulling down a stage3, as it uses python on the CD itself.
(In reply to comment #6) > It would pretty much have to be either: > > #1 - some crazy kernel incompatibility > #2 - hardware > > Try running mirrorselect from the CD, without pulling down a stage3, as it uses > python on the CD itself. > Just typed mirrorselect after boot up of the cd: No errors. Tried mirrorselect also before, to insert mirrors into make.conf. No problems at all from cd.
Find the problem in /usr/lib/python2.4/random.py: # Orginal-Zeile # NV_MAGICCONST = 4 * _exp(-0.5)/_sqrt(2.0) NV_MAGICCONST = 4 * _exp(-0.5) / 1.4145 Commented out the first original line. _SQRT(2.0) caused the error message. So I replaced it by its value. And now emerge (and others) work. What's the real problem?
Dunno... but it is definitely an issue with python itself... Python team: If this has already been fixed, then reassign to release so we can keep it open until a new release has been made with the fixed version.
Can we determine if this has been FIXED in 2007.0 or not?
No response in 5 months...
