I was updating my installed version of node.js this past weekend and ran in to a few problems, turns out due to the node team's decision to switch from the waf build system to gyp, there is now a Python 2.6+ dependency in the configure script.
On some webfaction boxes, the Python version that responds to "python" in env is 2.4, so you'll need to tell it where to look for the right version. The configure script looks for python in /usr/bin/env - here's the easiest way to get things working (worked for me) - people with better knowledge of Linux sysadmin type stuff will no doubt be able to improve this with a better alternative!
I’m going to be writing a new updated guide to setting up node.js on Webfaction shortly, but a quick tip that had me caught up last night while upgrading node to 0.8.1 from 0.4.11 on my Webfaction server:
In the 0.8 branch, node moved away from the waf build system to use gyp. A dependency of gyp is Python 2.6+, so if you just run the configure script on some webfaction boxes, it will fail.
You need to make sure it uses Python 2.6 or 2.7, so do this:
If it’s > 2.6, you can skip the rest of this and just install node! If it’s <2.6…
(Should display the version matching the one you downloaded!)
(X-Posted this on my site: http://davestevens.us/post/26911399072/nodejs-requires-python2-6-webfaction)
This question is marked "community wiki".
Thank you very much, this worked for me
answered Jul 19 '12 at 12:14
Found quicker to change the hardlink to python 2.6v during the installation.
Return back to old version.
answered Oct 09 '12 at 17:28