-
Notifications
You must be signed in to change notification settings - Fork 553
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
[XGBoost] Issues on Mac #778
Comments
OK, one strange thing: There was a comment from @staticfloat on dmlc/XGBoost.jl#68 saying " on MacOS, we are using clang to build Julia .... Using gcc on MacOS will cause us to mix C++ stdlibs, and I don't think that's a good thing" However, the build_tarballs.jl even prior to #657 doesn't seem to have this special casing for Mac. Elliot, was there any local uncommitted changes when you built these binaries, by any chance? |
We can just disable openmp and use clang for now. |
Btw are we ok on using the right commit for the build? |
Maybe I'm missing something, but what do you refer to? I only see v0.82 built last week |
The build script existed before. I only updated it. |
So the new script has
While the script linked by @giordano does not have these lines. I am still confused -- does removing these lines make it use clang on mac but gcc everywhere else? |
Yes, by default we use GCC for Linux and Windows, Clang for macOS and FreeBSD |
Is there a |
Not that i know. This issue can be closed, a new version has been released with clang compiled mac (without openmp) for v0.82 |
The latest build of XGBoost built in #657 fails to pass tests on the Mac. The error is as follows:
Full Test Results | #657
@ViralBShah says: there were many scary error messags in the Mac build
The previous binary builder builds, built by @staticfloat and available here https://github.com/JuliaBinaryWrappers/XGBoost_jll.jl/releases did work. However, the new version built into the jll as a result of #657 no longer works. It is not clear what has changed. As a short term fix, if we can get those binaries into a
jll
, we could move forward.cc: @giordano
The text was updated successfully, but these errors were encountered: