Summary: | Can't emerge portage: Illegal instruction in setup.py | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pierre-Olivier Bouchard <pete> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | python |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pierre-Olivier Bouchard
2004-04-07 16:16:10 UTC
Looks like a python problem to me, sure you used the right stage tarball ? I tried re-emerging python, and it didn't change a thing. The only ebuild I can't fully merge is portage, all others work fine. This system has been installed over a year ago, and has worked fine until about the time were portage 2.0.50-r2 was out, then retracted a few hours later. I was able to fix this: I commented out a test for the missingos module (whatever that is), and I was able to merge portage fine. Everything is working good since then (It's been a week or two since I fixed it, so I don't remember the line numbers I commented out to fix it. There doesn't seem to be any more lines about missingos in the ebuild.sh I currently have). It very much sounds like your using the wrong stage tarball. As the test is a python script and the missingos module is C code, there aren't a lot more options. As you never answered that question, that is what I'm going with. Reopen if you believe it otherwise. |