If I emerge a lot of files like 'emerge -e system' all packages might be re-emerged but mostly it ends with an error in an environment file in any random package. Looking at the environment file a space might have become a NULL and I also have an example where an e has become E alas 0x20 has been subtracted from the character. Reproducible: Sometimes I have gotten some help via the forum to resolv this; It can be found at <http://forums.gentoo.org/viewtopic-t-721934.html>
Created attachment 176726 [details] emerge error, space has become NULL.
Created attachment 176727 [details] Portage error where space has become NULL
Created attachment 176728 [details] emerge error where e has become E
I've never seen anything like it. It seems like bash or the python script that filters the environment is misbehaving, either due to some hardware or software corruption. Rebuild bash and python to see if that helps. If that doesn't help, extract a stage3 somewhere and chroot into it, as if you're doing a fresh install. Run emerge -e system in there to see if you experience the same problem in the chroot. If you can reproduce the problem inside the chroot then it has to be related to your hardware or your kernel.
(In reply to comment #4) Unfortunate for me I still get the error inside the chroot, so I guess I have to go out and get some new hardware.
