Hi all... I've been having a bit of grief with the latest AMD64 stages, in particular with gnome-doc-utils (all present versions). The error log was: Making all in doc make[1]: Entering directory `/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc' Making all in gnome-doc-make make[2]: Entering directory `/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc/gnome-doc-make' msgfmt -o de/de.mo de/de.po if ! test -d de/; then mkdir de/; fi if [ -f "C/gnome-doc-make.xml" ]; then d="../"; else d="/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc/gnome-doc-make/"; fi; \ mo="de/de.mo"; \ if [ -f "${mo}" ]; then mo="../${mo}"; else mo="/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc/gnome-doc-make/${mo}"; fi; \ (cd de/ && \ PYTHONPATH="/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc/gnome-doc-make/../../xml2po:/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc/gnome-doc-make/../../xml2po:" "/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc/gnome-doc-make/../../xml2po/xml2po/xml2po" -m docbook -e -t "${mo}" \ "${d}C/gnome-doc-make.xml" > gnome-doc-make.xml.tmp && \ cp gnome-doc-make.xml.tmp gnome-doc-make.xml && rm -f gnome-doc-make.xml.tmp) File "/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc/gnome-doc-make/../../xml2po/xml2po/xml2po", line 145 print VERSION ^ SyntaxError: invalid syntax make[2]: *** [de/gnome-doc-make.xml] Error 1 make[2]: Leaving directory `/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc/gnome-doc-make' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/portage/app-text/gnome-doc-utils-0.20.1/work/gnome-doc-utils-0.20.1/doc' make: *** [all-recursive] Error 1 * ERROR: app-text/gnome-doc-utils-0.20.1 failed: * compile failure I also had issues with other Python-related packages... further investigation, I discovered that Python 3.1 was selected as the system version of Python. Setting this to 2.6 via eselect fixed the problem. The version information I have is: beast install # ls stage3-amd64-20100729.tar.bz2 stage3-amd64-20100729.tar.bz2.DIGESTS stage3-amd64-20100729.tar.bz2.CONTENTS stage3-amd64-20100729.tar.bz2.DIGESTS.asc beast install # cat *.DIGESTS # MD5 HASH 496d7a2977dcd5f035d729c9e5c76b24 stage3-amd64-20100729.tar.bz2 # SHA1 HASH f04ba7c7bdb66900a82cccc7fa3bb54707104629 stage3-amd64-20100729.tar.bz2 # MD5 HASH 3da676d1e8f94bd0158b39f1c6360af1 stage3-amd64-20100729.tar.bz2.CONTENTS # SHA1 HASH afd9c92bde22b485f244ddcc49588bdcd82a2a1e stage3-amd64-20100729.tar.bz2.CONTENTS If people wind up with issues like the above when compiling packages, they should try an `eselect python set python2.6`, particularly if `python --version` reports Python 3.1.
*** This bug has been marked as a duplicate of bug 330655 ***