-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
XGBoost4j missing dylib for apple sillicon m1 #7501
Comments
Currently XGBoost4J does not support Apple Silicon. Sorry for inconvenience. |
Got it, can you provide some kind of timeline here? |
@martintreurnicht We don't know yet. None of us (XGBoost developers) own an M1 machine, and currently I am not aware of any CI service that lets you test Apple Silicon. |
You can compile xgboost4j from source on an M1 machine and it works. I did this last year when they came out on my personal M1 MBP, but without build resources to make the binaries it's hard to deploy. This PR I wrote from January modifies the loader so you can package the aarch64 dylib in to a jar file containing an x86 one (and the other OS binaries as well) and everything works, so you can push that to an internal artifactory if you have one. |
@Craigacp Ok awesome, thanks! Yeah I got it to build and works great. I now just need to combine this dylib with the existing jar. This will unblock us for now |
@hcho3 I see you guys use github actions, you can probably use something like https://www.macstadium.com/mac-mini. Setup self-hosted with mac stadium should do the trick |
Thanks for the pointer. We'll revisit once we have enough bandwidth and funding (since we'd have to pay MacStadium) |
Ok fully understand, is there no way to cross compile this on |
I think cross-compiling the JNI binding will be tricky. You'll probably need to have an ARM64 JVM as well as an x86 one to ensure you have the right libraries to link against. |
Closing as duplicated to #6408 |
CPU:
Apple M1 Max
RAM:
64GB
java -version
:LIBRARY:
ml.dmlc:xgboost4j_2.12:1.5.1
Getting the following error when trying to run our model tests.
Seems like the root cause at the bottom of the stacktrace is a missing dylib:
Is there a known fix for this?
The text was updated successfully, but these errors were encountered: