Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node-gyp --no-parallel option breaks build #1981

Closed
zencodism opened this issue May 6, 2014 · 14 comments

Comments

@zencodism
Copy link

commented May 6, 2014

On Ubuntu Trusty LTS build stops with quite a lot of gyp and npm errors, starting with 'unknown option --no-parallel'.

I searched for that option and commented it out in
./build/node_modules/npm/node_modules/node-gyp/lib/configure.js
and
./build/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/init.py

After that, build commenced and finished without errors. Being on this particular Ubuntu version I had also make symlinks for 'node' binary and libudev.so.0, but afterwards Atom runs happily.

So the question is, is the no-parallel option really important? Anyone else had similiar issues? Is the removal of these two lines a right thing to do?

@matheusmessora

This comment has been minimized.

Copy link

commented May 7, 2014

It apperts Ubuntu 14 ships with Python2.7, and this doens't work well with this installation.
Try installing Python2.6 and point the command that is in the README to python2.6
I'm still running with sudo. I'll try the answer by @chasingmaxwell and see if it works without sudo.

http://stackoverflow.com/questions/21155922/error-installing-node-gyp-on-ubuntu

npm config set python /usr/bin/python2.6 -g

#1814 (comment)

@davidlgj

This comment has been minimized.

Copy link

commented May 7, 2014

On Ubuntu 14.04 building having the gyp package installed can also trigger the same error
sudo apt-get remove gyp fixed it for me.

@htor

This comment has been minimized.

Copy link

commented May 7, 2014

Same situation here on Debian Sid 3.14.

I made it work by commenting out argv.push('--no-parallel') in atom/build/node_modules/npm/node_modules/node-gyp/lib/configure.js and creating a symlink /lib/libudev.so.0 to /lib/libudev.so.1. Also, I had to chmod +x /usr/local/bin/atom to make it executable.

@jmcomets

This comment has been minimized.

Copy link

commented May 7, 2014

Having the same problem here, using python2.6 doesn't fix it.

@george-b

This comment has been minimized.

Copy link

commented May 7, 2014

I did the same as @davidlgj and @htor removing gyp and adding the symlink for libudev allowed me to get Atom running on Ubuntu 14.04.
Also for what it's worth I don't think python 2.6 is in the Ubunutu 14.04 repos so asking people to compile another build of python and switch back and forth with update-alternatives seems a bit of hassle.

@jmcomets

This comment has been minimized.

Copy link

commented May 7, 2014

Got it to work on trusty the same way as @htor did.

@tessi

This comment has been minimized.

Copy link

commented May 7, 2014

I got it to work using a current master (61fff23) on Ubuntu 14.04 without changes to the atom code through removing the system-node (+ npm and related packages) and manually building node (v0.10.26) from source and installing npm (1.4.10).

@Volox

This comment has been minimized.

Copy link

commented May 7, 2014

+1

@rhoconlinux

This comment has been minimized.

Copy link

commented May 7, 2014

+1 for @htor
also worked for me :)
http://i.imgur.com/CAvdAHg.png

@kelunik

This comment has been minimized.

Copy link
Contributor

commented May 8, 2014

@davidlgj's solution worked for me. It worked two days ago without any change, but didn't today until I removed that package.

@probablycorey probablycorey added the linux label May 9, 2014

@zencodism

This comment has been minimized.

Copy link
Author

commented May 12, 2014

@djfm Your solution is exactly what I did and described in the first post here, opening the issue. Perhaps I should be more clear or specific, I guess :)

@djfm

This comment has been minimized.

Copy link

commented May 12, 2014

@zencodism very true, sorry! Must have read it too quickly. Just removed my comment :)

@kevinsawicki

This comment has been minimized.

Copy link
Member

commented May 16, 2014

Closing this out since with the solution to upgrade gyp and node-gyp as mentioned here nodejs/node-gyp#426

@lock

This comment has been minimized.

Copy link

commented Jan 25, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 25, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
You can’t perform that action at this time.