>>> Emerging (1 of 2) net-libs/nodejs-0.4.8 * node-v0.4.8.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * Package: net-libs/nodejs-0.4.8 * Repository: gentoo * Maintainer: patrick@gentoo.org schamane@myeburg.net * USE: amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: sandbox >>> Unpacking source... >>> Unpacking node-v0.4.8.tar.gz to /var/tmp/portage/net-libs/nodejs-0.4.8/work >>> Source unpacked in /var/tmp/portage/net-libs/nodejs-0.4.8/work >>> Preparing source in /var/tmp/portage/net-libs/nodejs-0.4.8/work/node-v0.4.8 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/net-libs/nodejs-0.4.8/work/node-v0.4.8 ... Traceback (most recent call last): File "/var/tmp/portage/net-libs/nodejs-0.4.8/work/node-v0.4.8/tools/waf-light", line 157, in <module> import Scripting File "/var/tmp/portage/net-libs/nodejs-0.4.8/work/node-v0.4.8/tools/wafadmin/Scripting.py", line 146 except Utils.WafError, e: ^ SyntaxError: invalid syntax * ERROR: net-libs/nodejs-0.4.8 failed (configure phase): * (no error message) * * Call stack: * ebuild.sh, line 56: Called src_configure * environment, line 2159: Called die * The specific snippet of code: * ./configure --shared-v8 --prefix=/usr || die * * If you need support, post the output of 'emerge --info =net-libs/nodejs-0.4.8', * the complete build log and the output of 'emerge -pqv =net-libs/nodejs-0.4.8'. * The complete build log is located at '/var/tmp/portage/net-libs/nodejs-0.4.8/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-libs/nodejs-0.4.8/temp/environment'. * S: '/var/tmp/portage/net-libs/nodejs-0.4.8/work/node-v0.4.8' >>> Failed to emerge net-libs/nodejs-0.4.8, Log file: >>> '/var/tmp/portage/net-libs/nodejs-0.4.8/temp/build.log' * Messages for package net-libs/nodejs-0.4.8: * ERROR: net-libs/nodejs-0.4.8 failed (configure phase): * (no error message) * * Call stack: * ebuild.sh, line 56: Called src_configure * environment, line 2159: Called die * The specific snippet of code: * ./configure --shared-v8 --prefix=/usr || die * * If you need support, post the output of 'emerge --info =net-libs/nodejs-0.4.8', * the complete build log and the output of 'emerge -pqv =net-libs/nodejs-0.4.8'. * The complete build log is located at '/var/tmp/portage/net-libs/nodejs-0.4.8/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-libs/nodejs-0.4.8/temp/environment'. * S: '/var/tmp/portage/net-libs/nodejs-0.4.8/work/node-v0.4.8' * Build finished correctly. Removing temporary files... * You can re-run revdep-rebuild to verify that all libraries and binaries * are fixed. Possible reasons for remaining inconsistencies include: * orphaned files * deep dependencies * packages installed outside of portage's control * specially-evaluated libraries
(In reply to comment #0) > >>> Emerging (1 of 2) net-libs/nodejs-0.4.8 > * node-v0.4.8.tar.gz RMD160 SHA1 SHA256 size 1) Please attach that file. 2) Please post your `emerge --info' output too.
Created attachment 276569 [details] emerge --info output
nodejs-0.4.8.tar.gz here http://rghost.net/10304951
Comment on attachment 276569 [details] emerge --info output (In reply to comment #3) > nodejs-0.4.8.tar.gz here http://rghost.net/10304951 Please attach the log, don't put it in a tar ball and do not compress it either - it's small enough as it is.
> (In reply to comment #3) > > nodejs-0.4.8.tar.gz here http://rghost.net/10304951 > > Please attach the log, don't put it in a tar ball and do not compress it either > - it's small enough as it is. Er, wait. You uploaded a widely distributed source tar ball that our ebuilds have perfectly valid SRC_URI values for? Oh. I was really referring to the log that you posted in the Description and that for some reason got completely mangled. Attach /that/.
Created attachment 276667 [details] nodejs-0.4.8 buildlog
nodejs-0.4.9 - still same error
for "fix" this error you need choose python2.7 as wide system python interpreter. This error shown only when python3.1 choosed
Python-3 doesnt suppose to work with current portage...
(In reply to comment #9) > Python-3 doesnt suppose to work with current portage... All other ebuilds works ok. except nodejs.
Created attachment 280181 [details, diff] fix for node working with python3 as the default python.
(In reply to comment #11) > Created attachment 280181 [details, diff] > fix for node working with python3 as the default python. Note that this tells node.js to use python2, and adds a python2 dep. I figure that by the time people are eliminating python2 from their systems entirely, node.js will be compatible with python3, so this fix should work until node.js is ready for python3.
Please also see bug #364629 that is maybe a duplicate of this bug, but it has better ebuilds using the python eclass instead of manual sed.
+ 20 Feb 2012; Patrick Lauer <patrick@gentoo.org> nodejs-0.6.11.ebuild: + Restrict python to 2.*
