-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Fix $MACOSX_DEPLOYMENT_TARGET #3337
Conversation
@devin-petersohn @raulchen Can you test if this PR fixes your problem? You might need to start in a clean environment (i.e. no old build files should be present). |
Test FAILed. |
Test PASSed. |
It also could not work in my case. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my case, I add another module which will be built into Ray.
A third-party lib need check the version of system in my adding module.
It will fail reasonably because of the fixed system version.
build.sh
Outdated
@@ -106,6 +106,7 @@ pushd "$BUILD_DIR" | |||
make clean || true | |||
rm -rf external/arrow-install | |||
|
|||
export MACOSX_DEPLOYMENT_TARGET=10.7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still don't think setting the TARGET to a fixed number is a good idea.
With this change, I'm getting the following error:
|
But if I only remove the |
+1 to @raulchen's comment; removing the
|
Yeah I think you are right, I adapted the PR. The set seemed to be necessary when I added the libc++ to fix compilation on 10.14, but I just tested it there and it doesn't seem necessary. |
Test FAILed. |
Hmmm, now travis doesn't like it:
I wonder what the right solution here is. |
Test FAILed. |
This should fix the
error. I made sure it still compiles under 10.14 but haven't been able to test if it fixes above error (since I can't reproduce that error).
Related issue: #3315