-
Notifications
You must be signed in to change notification settings - Fork 29
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
Failed install on Mac #2
Comments
Could you compare these two files:
I don't have the second one on my Mac, I think your system is using it in the build when the first one should be used. We could verify Xcode-select is setup correctly:
the output on my Mac is:
|
OK, the two files are the same contents EXCEPT the path for my file is above and your path is below
This looks good
|
Ok, that's the path I have as well (I accidentally replaced the X). Hmm, might be a compiler issue then? What's the output of
|
|
Even though you have the Xcode command line tools installed, you're using the MacPort gcc. On my Mac:
Try setting the path, just before npm install:
This should switch you back to using the Apple gcc for the rest on the terminal session. |
Worked perfectly. Thanks for helping me through this issue. |
I'm still having the same problem. which gcc is /usr/bin/gcc Mac OS X 10.9.3 |
@LeslieOA are you sure? What's the output of |
Hey Sandeep.
|
That's the same as mine. Is your error the exact same as Matt's first comment? |
Not exactly, but it does seem xpc-connection related.
|
Ok, it's the same as: stormboy/node-zbee#4 (comment) What does your path look like? (
|
@sandeepmistry, your last comment about the path cleaned this up for me. My $PATH is quite abused, resetting it to yours resolved an issue I had today on Yosemite. Thank you. |
@zdennis no problem! Do you think this should be added to the read me? |
@sandeepmistry, I think that would be helpful as common thing to try before filing an issue. |
Getting the following error on install
Originally reported as error at noble/noble#75 but tracked to this package.
The text was updated successfully, but these errors were encountered: