-
-
Notifications
You must be signed in to change notification settings - Fork 11.4k
node failed to build on 10.10 #33484
Comments
I'm having the same problem today. I was able to fix these: but I'm still getting
|
Try murdering your Node install and then doing |
Hmm I'm still getting this at the end |
I am actually doing a clean install. |
Removing node, npm, and all modules before doing a clean install with homebrew worked for me. I removed files in the following locations: |
It works. I had formatted my hard drive to clean install Yosemite, but did copy the ~/.npm folder to my home folder. Erasing it solved the problem. |
Is everyone here successfully building now, or is anyone still having trouble with Node? |
@DomT4 I'm wondering why |
On Yosemite (upgraded from Mavericks), I was able to murder my node as @DomT4 suggested but I'm getting the following when running
However after running |
@rkz Try |
@MikeMcQuaid Same. |
If it wasn't for the |
I'm clean installing Mavericks, so I should be good. |
Turns out I was able to finish the install by adding |
I had the same problem and solved it by following @DomT4's suggestion. After that I reinstalled gulp, http-server and yeoman: |
That command will print all the versions of packages that are installed, as well as their dependencies, in a tree-structure. That's probably why there's more modules listed than you're expecting. |
I had the same issue but it seems that the core problem is that it failed when it was trying to create a symlink for dtrace:
I ran |
dtrace is one of those directories that crops up quite often as a little hellraiser. It can usually be fixed with |
I should also note that when I uninstalled node using |
DomT4's comment worked for me (running the shell script and then reinstalling through brew) |
@thomchop I missed your post above before, but thanks for the reminder about npm's love of trees. I've pushed a new commit to my script to ensure people aren't getting enormous readouts on that. Glad the script is still useful. Node ❤️ root permissions when it installs through the .pkg, so any traces on a system of that tend to cause hell given Brew deliberately isn't run as root and can't override those. |
@DomT4 I am having this issue and use every solution provided here except your script. How does one go about running your script in the terminal? |
Nevermind, I got it: |
@brianllamar Apologies, I did leave a hint on how to make the script executable on the page, but I didn't hint as to how to actually execute it. I'll push a fix for that clarification shortly. As you discovered you can either do |
|
No matter what I do I always get hung up at this step: $ brew postinstall node node cli.js rm npm -g -f |
@swells808 Either kill Node entirely and try again, or do |
Tried to kill it. Here is the link https://gist.github.com/5a34b780b4ffe077da11 |
Try |
and again: rmdir /usr/local/include To force the link and overwrite all conflicting files: To list all files that would be deleted: Possible conflicting files are: |
Are you sure you tried the script? Those directories would be gone with the script. Try:
|
Is there a primary issue still being tracked here, or are people just posting random failures? |
Nope. It's Sgt. Pepper's Not-So-Lonely Random Node Failures Club Band. Can probably be closed, if so desired. |
brew install node throws warning when making npm:
npm ERR! Additional logging details can be found in:
npm ERR! /usr/local/lib/node_modules/npm/npm-debug.log
npm ERR! not ok code 0
make[1]: *** [node_modules/.bin/ronn] Error 3
make: *** [man/man3/npm-bin.3] Error 2
Warning: The post-install step did not complete successfully
You can try again using 'brew postinstall node'
After command
brew postinstall node
it throws the same npm building error message and points towards troubleshooting gitpage.Following instructions there I've updated Xcode and CLT, and searched for open tickets on node and npm. I found nothing.
The problem: npm doesn't build. There are binaries, but when running it shows activity, but does nothing.
The gist-log is the following:
https://gist.github.com/abcsds/6082952c83a166ca0f06
The text was updated successfully, but these errors were encountered: