-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[homebrew] Default install environment gives linker errors #2417
Comments
IIRC Homebrew pushes for recent libc++ for osx 10.9+.. While installing with homebrew, you should use |
Homebrew lead maintainer here: can you elaborate on what this means as I'm not sure I understand.
We consider |
|
Incidentally, the fact that |
Also, it's a bit sketchy a new formula is using libstdc++ and that c++11 kills it. |
I might remember this wrong but Homebrew build sets |
We set the environment variable MACOSX_DEPLOYMENT_TARGET to the same as the host. |
CC build script sets macos deployment target to 10.7 in order not to introduce libc++/libstdc++ mix into ChakraCore dependent solutions. These solutions similarly target 10.7 SDK. Apart from that, there is no particular reason for us to pick libstdc++ over libc++ at the moment. At least, I'm not aware any other reason.
In that case; Upcoming change to our build script; |
@obastemur cool. It would be great if we could build with ENV.cxx11 set, which passes Any idea why ChakraCore isn't happy with |
No particular reason, just a bug. Fixed on CC end. Suspicious behavior though. All these changes will be part of upcoming xplat release. |
@obastemur nice work! With the patch, -Os succeeded. However, if I (on macOS 10.11)
I get
|
@ilovezfs you don't need to replace anything. Right now, on the master branch, if |
@mathiasbynens Thanks for opening this up! @ilovezfs @MikeMcQuaid Thanks for all the help to figure out the issues. Merging the PR closed this issue automatically. Both |
While working on a Homebrew formula for ChakraCore, I ran into an issue when running
./build.sh --static --test-build --no-icu
. Running that command on its own (outside of the Homebrew sandbox) works fine, but within the sandbox, the linking step fails with the following error:Since the command works outside of the sandbox, I figure I’m doing something wrong here. Any ideas what to look for? Here’s some more info about the sandbox environment in which the linking fails:
Here’s the full log: https://bot.brew.sh/job/Homebrew%20Core/15413/version=el_capitan/testReport/junit/brew-test-bot/el_capitan/install_chakra/
The text was updated successfully, but these errors were encountered: