-
Notifications
You must be signed in to change notification settings - Fork 255
Unable to build on OSX 10.11.1 #244
Comments
same problem here any fix? |
Me too! I even tried using a docker... didn't work. |
I have a fix! Well at least this worked for me. I'll provide step by step on what I did. First, I looked into issues with node-gyp. I first installed it using npm by doing From this point, write
Then in terminal type After, we must update the npm config as well to support this. Write the following commands into terminal:
The final line is just to make sure the settings were inputted into the config. The final step (you may of have to earlier) is to make sure you have XCode AND XCode Command Line Tools installed. If you don't know how, first install the latest version of XCode from the app store. Next in terminal type At this point you should have all of the essential tools to try installing airsonos or any other npm packages that require node-gyp. However, if you are currently in the same boat as I was, please install node-gyp install like so:
Essentially what node-gyp-install does is manually install all of the node/iojs header files that are needed for node-gyp to work properly. After I did, as a wrap-up, I had no issue installing airsonos/mdns/all of those npm packages that depend on node-gyp. This ends my fix. Currently I'm still getting the bug where it either hangs on |
I ended up getting it to work without all that hastle and without any python commands or the full XCode. Ill try to backtrack and figure out what i had to do to install it. If i remember correctly, manually installing it rather than using npm was the solution. I will have to double check the terminal history when i get home, but this looks familiar. All i had to do was run this command: sudo npm install -g --unsafe-perm airsonos |
Essentially my way is doing it involving npm. Your way is very promising as well, and I agree is probably easier. However, my fix works with all npm packages that require |
after all this time... I can't make it work. Now thanks to @colinrioux, it works now. Thanks bro. just these 3 lines, voilà!
|
I have found
|
I am receiving this error as well... probably first step to try is to unplug the bridge and link a speaker via ethernet (to the back of your router). If that doesn't work, its best to watch the issues page for possible fixes from people. |
Thanks for the solutions guys! I'll give it a go this weekend again. It
|
the bridge is the culprit. after removing the bridge out of the system, it works again. no more |
This is great! It installed perfectly after following Colin's instructions. One additional step - if you get an error regarding connection reset then you need to change npm configs to use http instead of https:
Ironically, SONOS is launching apple music on beta tomorrow. But this is better! :) Cheers everyone for all the help (and to the author for this awesome hack)! |
@colinrioux, beautiful! Thanks so much! I couldn't get |
Getting same error as bezwu and ColinRioux from bluebird when SONOS bridge is installed. Without Bridge no problems but ... alas neither speakers, since those are addressed via the bridge. |
I didn't have these installation problems, but @colinrioux did help me realize I didn't have |
I was unable to build on El Capitan. I'm attaching the debug log output. Can someone please help?
npm ERR! [email protected] install:
node-gyp rebuild
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls mdns
npm ERR! There is likely additional logging output above.
npm-debug.log.txt
The text was updated successfully, but these errors were encountered: