I'm running Node 0.6.15 on CentOS with Python 2.4.3 and for some reason, I'm getting this weird error while trying to install 0.8.1 Does anyone have any idea on what can I do about it?
$ cd node-v0.8.1 $ ./configure File "./configure", line 266 o['default_configuration'] = 'Debug' if options.debug else 'Release' ^ SyntaxError: invalid syntax
On Sat, Jun 30, 2012 at 3:19 AM, neojp <thene...@gmail.com> wrote:
> Hey guys,
> I'm running Node 0.6.15 on CentOS with Python 2.4.3 and for some reason, I'm
> getting this weird error while trying to install 0.8.1
> Does anyone have any idea on what can I do about it?
> $ cd node-v0.8.1
> $ ./configure
> File "./configure", line 266
> o['default_configuration'] = 'Debug' if options.debug else 'Release'
> ^
> SyntaxError: invalid syntax
>> I'm running Node 0.6.15 on CentOS with Python 2.4.3 and for some reason, I'm
>> getting this weird error while trying to install 0.8.1
>> Does anyone have any idea on what can I do about it?
>> $ cd node-v0.8.1
>> $ ./configure
>> File "./configure", line 266
>> o['default_configuration'] = 'Debug' if options.debug else 'Release'
>> ^
>> SyntaxError: invalid syntax
> You need to use python 2.6 or 2.7.
Shouldn't the configure script print a friendlier message if a wrong version of python is used?
>>> I'm running Node 0.6.15 on CentOS with Python 2.4.3 and for some reason, I'm
>>> getting this weird error while trying to install 0.8.1
>>> Does anyone have any idea on what can I do about it?
>>> $ cd node-v0.8.1
>>> $ ./configure
>>> File "./configure", line 266
>>> o['default_configuration'] = 'Debug' if options.debug else 'Release'
>>> ^
>>> SyntaxError: invalid syntax
>> You need to use python 2.6 or 2.7.
> Shouldn't the configure script print a friendlier message if a wrong version of python is used?
Chicken/egg problem. configure is a python script, it's the python
interpreter that raises the error.
I guess we could wrap it in a shell script that checks the python
version but I don't find that very appealing. The build requirements
are clearly documented in the README but that's not the main reason: I
don't like layers upon layers, it makes debugging harder.
On Fri, Jun 29, 2012 at 9:43 PM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
> > Shouldn't the configure script print a friendlier message if a wrong
> version of python is used?
> Chicken/egg problem. configure is a python script, it's the python
> interpreter that raises the error.
> I guess we could wrap it in a shell script that checks the python
> version but I don't find that very appealing. The build requirements
> are clearly documented in the README but that's not the main reason: I
> don't like layers upon layers, it makes debugging harder.
On Fri, Jun 29, 2012 at 7:26 PM, Matt <hel...@gmail.com> wrote:
> On Fri, Jun 29, 2012 at 9:43 PM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
>> > Shouldn't the configure script print a friendlier message if a wrong
>> > version of python is used?
>> Chicken/egg problem. configure is a python script, it's the python
>> interpreter that raises the error.
>> I guess we could wrap it in a shell script that checks the python
>> version but I don't find that very appealing. The build requirements
>> are clearly documented in the README but that's not the main reason: I
>> don't like layers upon layers, it makes debugging harder.
On Sun, Jul 1, 2012 at 2:34 AM, <r...@tinyclouds.org> wrote:
> On Fri, Jun 29, 2012 at 6:23 PM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
>> You need to use python 2.6 or 2.7.
> It would be preferable to support Python 2.5 in our build scripts if
> possible. Does GYP?
Not anymore. They made 2.6 a requirement some months ago.
Thanks Ben, I'll update Python and let you know if this fixes my problem.
It is funny though, I couldn't find any requirements information on the site. Obviously I didn't look at the README.md<https://github.com/joyent/node>on Github, but so far, I've installed node in so many boxes and never thought about what version of Python was required, or that Python was required at all.
I totally agree about not wanting to have a python version check wrapper on top of the real configure. But, having a requirements info in the download link at the website would have saved me some time.
Thank you guys, you rock the server side Javascript world.
On Sun, Jul 1, 2012 at 6:09 AM, neojp <thene...@gmail.com> wrote:
> Thanks Ben, I'll update Python and let you know if this fixes my problem.
> It is funny though, I couldn't find any requirements information on the
> site. Obviously I didn't look at the README.md on Github, but so far, I've
> installed node in so many boxes and never thought about what version of
> Python was required, or that Python was required at all.
> I totally agree about not wanting to have a python version check wrapper on
> top of the real configure. But, having a requirements info in the download
> link at the website would have saved me some time.
That's a good idea. I've opened an issue for it[1].
> And I'm guessing it's playing a part in why I can't install the newest
> version of Node.js since I can't get past ./configure (where other
> packages/installs succeeded when ./configure was entered).
You may have installed python 2.7 but you're not using it, otherwise
you wouldn't be getting that error. :-)
Try this:
$ python2.7 configure
$ make PYTHON=python2.7
Replace python2.7 with whatever the binary is really called.
