-
Notifications
You must be signed in to change notification settings - Fork 1
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
Compilation of the library under Anaconda (CI) #4
Comments
I think it's a mac osx arm64 error call because in Test (macos) step, 5th step, the call is to run rustup target add x86_64-apple-darwin |
When installing Anaconda, the reported platform is |
I have it as working on arm64 rustc 1.76 as long as the |
I added
to print additional information but I still don't understand the cause of the problem. Glad that it works for you. For the Polars problem, you may want to add your voice. |
If I specify arm-86, I get the error error: command failed: 'cargo': Bad CPU type in executable (os error 86). |
This type of error is referred to in the Pyo3 doc! But it does not seem to be related to our problem... |
I've added a MacOS aarch64 worker to the CI and it works fine. |
I also added anaconda on arm64... and it fails the same way as for amd64. For now, I allowed it to fail. 😢 |
Not sure of the issue...could try miniconda instead which is lighter and I am using. |
Thanks for your reply. That's what I am using for MacOS arm64 because the worker (provided by FlyCI) does not come with Anaconda installed. Unfortunately, the end result is the same. It's a really frustrating error as it used to work and it is not clear what changed... |
Yes I am not clear on the issue, I think we will need to post on conda website, because it works locally. |
Now I have an error that resembles to one of |
See also rust-lang/cargo#12670 |
The problem was the |
DYLD_LIBRARY_PATH specification was indeed all that was needed to fix locally |
Unfortunately, that is also was was causing the problem for the CI. Let's hope it is fixed at the PyO3 level — or at the anaconda level. This issue is already 4.5 years old... |
Well, all tests (including using anaconda) now pass but they depend on a "link trick":
|
The continuous integration test for Anconda is failing. @LCrossman If you have time (and since you use Anaconda — I don't),
The text was updated successfully, but these errors were encountered: