Bug 370967 – net-libs/nodejs with python3.1 - invalid syntax

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Anton Kochkov 2011-06-10 01:00:23 UTC]

>>> 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: [e-mail] [e-mail]
	 * 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

[Comment 1 Jeroen Roovers (RETIRED) 2011-06-10 14:54:31 UTC]

(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.

[Comment 2 Anton Kochkov 2011-06-10 19:25:05 UTC]

Created attachment 276569 [details]
emerge --info output

[Comment 3 Anton Kochkov 2011-06-10 19:31:47 UTC]

nodejs-0.4.8.tar.gz here http://rghost.net/10304951

[Comment 4 Jeroen Roovers (RETIRED) 2011-06-11 14:59:49 UTC]

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.

[Comment 5 Jeroen Roovers (RETIRED) 2011-06-11 15:03:19 UTC]

> (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/.

[Comment 6 Anton Kochkov 2011-06-11 15:09:10 UTC]

Created attachment 276667 [details]
nodejs-0.4.8 buildlog

[Comment 7 Anton Kochkov 2011-07-03 04:25:00 UTC]

nodejs-0.4.9 - still same error

[Comment 8 Anton Kochkov 2011-07-03 04:26:19 UTC]

for "fix" this error you need choose python2.7 as wide system python interpreter. This error shown only when python3.1 choosed

[Comment 9 SchAmane 2011-07-03 10:28:34 UTC]

Python-3 doesnt suppose to work with current portage...

[Comment 10 Anton Kochkov 2011-07-03 10:49:30 UTC]

(In reply to comment #9)
> Python-3 doesnt suppose to work with current portage...

All other ebuilds works ok. except nodejs.

[Comment 11 Daniel Robbins 2011-07-16 17:41:41 UTC]

Created attachment 280181 [details, diff]
fix for node working with python3 as the default python.

[Comment 12 Daniel Robbins 2011-07-16 17:43:07 UTC]

(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.

[Comment 13 Alexander Sulfrian 2012-02-02 23:57:52 UTC]

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.

[Comment 14 Patrick Lauer 2012-02-20 13:21:00 UTC]

+  20 Feb 2012; Patrick Lauer <[e-mail]> nodejs-0.6.11.ebuild:
+  Restrict python to 2.*