node build fails on OS X 10.11 #40653
Comments
Apple appears to be shipping At least on my 10.10 system (upgraded from previous OS Xs), |
Also, for reference, I was able to install node on 10.11 using the Xcode 7 CLT without an issue. Maybe there's an issue with your setup? Can you provide the output of |
You are right, it looks like the reason this worked before is that the required symlinks exists in the OS X 10.10 SDK:
In the Xcode beta, they are gone:
The Xcode stable version is my current command-line SDK according to |
They're new to Xcode 7, and I don't believe there is any public documentation on them yet. |
That is probably the reason why the Xcode 6 toolchain did not pick these libraries/links up in the first place. This issue may just "go away" once Xcode 7 ships as default toolchain for OS X 10.11. Using the Xcode 7 toolchain, everything worked as expected:
Thank you for the quick feedback - lesson learned, early access software tends to bite :). Shall we leave this bug report open for future reference, or close right away? |
Ah, yep, that would be the reason. We don't support Xcode 6 on 10.11; you need to use Xcode 7 to build software on 10.11. I'll close this then, thanks! |
@mistydemeo Perhaps we should hard-error in that case? |
@MikeMcQuaid After #40536 is merged, maybe? We'd get a doctor warning there but hard erroring might be better than continuing to field these reports. |
@DomT4 ❤️ |
👍 for @mologie writeup. Saved me today. |
Saved my ass and I do believe we should keep it open. |
This issue should remain closed. As discussed in the comments, the issue was with my setup: Xcode 6 is not supported on OS X 10.11. Install Xcode 7 and configure Xcode 7 as default toolchain. With Xcode 7, node builds just fine without the workaround mentioned in my first post. |
I am seeing this error in my OSX 10.10 too. |
This occurred to me too in OSX 10.10 after I downloaded an updated command line tools. Updating Xcode to 7 fixed the issue for me too. |
Hate to ask on this thread, but I'm a little desperate. I'm having the same build issue for libjpeg-turbo since updating to Xcode 7 and El Captian (missing libgcc). The comment above mentions to set Xcode 7 as the default toolchain. What do you mean by setting it as the default toolchain? For instance, I'm using a configure and make style build for libjpeg-turbo. Is there another step I need to take to make this work with Xcode 7? |
@JoeyCarson Open a new issue with |
Well this isn't really dependent on brew, I'm building libjpeg-turbo from svn trunk for iOS and simulator. But when building it for the simulator, the same issue occurs, configure fails because it can't find libgcc. This thread mentions that the issue is fixed by setting Xcode 7 as the default toolchain. I have already installed the official Xcode 7 and my xcode-select -p shows the correct directory to it. |
My last comment from Jun 13 in this thread shows how to change the default toolchain from command line. You can also do so from Xcode -> Preferences... -> Locations -> Command Line Tools. |
Yes I just saw that. I do have my xcode-select pointing to the proper directory, so if that was your solution, then mine perhaps just shows the same symptom and not the same cause. |
+1 |
It helps to uninstall the older version of Xcode: Also freed up 4GB, wahey! |
+1 @mologie |
It is with luck that I found this ticket, because the way npm install fails when this occurs is really difficult to trace back to this problem. Anyone have ideas how the error reporting of node or gyp can be improved to make this more clear ? |
I'm getting this error same error in OSX 10.10 using xcode 6.4, just wondering if upgrading OSX and xcode is going to be easier than tracking down the cause in OSX 10.10/xcode 6.4. Edit: just to be clear, this is the error I get during a node-gyp build.
And in /Applications/Xcode.app/contents/.../lib/ I have:
|
Yes, it will be. |
I simply upgraded Xcode and that fixed the issue. So this issue is independent of OSX version. |
EDIT: This issue appears on Google now and seems to affect quite a few people. To spare you from reading the comments:
The solution for the issue described here is to install Xcode 7 and configure it as default toolchain. Xcode 6 is not supported on OS X 10.11.
This is likely an upstream issue in
node-gyp
: Apple removed the deprecated symlinks fromlibgcc*.dylib
tolibSystem.B.dylib
.Note that I have Homebrew installed under
$HOME/.local
, but considering the nature of the error, I would not deem this relevant. Installation with the same setup succeeds on OS X 10.10.Harmless workaround for us early adopters:
The text was updated successfully, but these errors were encountered: