Skip to content
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

ARM OSX Migrator #49

Conversation

regro-cf-autotick-bot
Copy link
Contributor

This feedstock is being rebuilt as part of the ARM OSX migration.

Feel free to merge the PR if CI is all green, but please don't close it
without reaching out the the ARM OSX team first at @conda-forge/help-osx-arm64.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot.
The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, feel free to drop us a line if there are any issues!
This PR was generated by https://github.com/regro/autotick-bot/actions/runs/562004941, please use this URL for debugging

@conda-forge-linter
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@ericmjl
Copy link
Contributor

ericmjl commented Feb 15, 2021

@conda-forge/help-osx-arm64 I looked at the builds, but couldn't decipher what was going on here. Because the jaxlib wheels are being copied directly from PyPI (that's what I remember), could it be that the wheels, which are pre-compiled, aren't compatible? If so, we might have to wait, perhaps, for XLA and then jaxlib to be compiled?

@erykoff
Copy link

erykoff commented Feb 15, 2021

Looking at the source, there's a chain of pre-compiled x86 binaries that go into jaxlib, so this isn't something we can directly make arm64 compatible.

@xhochy
Copy link
Member

xhochy commented Feb 26, 2021

We should probably switch this to a from-source build. https://jax.readthedocs.io/en/latest/developer.html#building-jaxlib-from-source gives the impression that this may not be too complicated.

@ericmjl
Copy link
Contributor

ericmjl commented Feb 28, 2021

@xhochy building from source is a bit of a pain. @ocefpaf tried it a while ago, but it didn't really work out. That said, I'm game to try again. @ocefpaf, do you have handy any notes for building jaxlib from source that I could study?

@ocefpaf
Copy link
Member

ocefpaf commented Mar 1, 2021

@xhochy building from source is a bit of a pain. @ocefpaf tried it a while ago, but it didn't really work out. That said, I'm game to try again. @ocefpaf, do you have handy any notes for building jaxlib from source that I could study?

Things changed a lot from the last time I tried (2 years ago!?). We should definitely try again.
@xhochy is that something you are interested in tackling? I have to confess I don't have much free time lately for non day-job work.

@xhochy
Copy link
Member

xhochy commented Mar 1, 2021

This possibly falls into my day job category but not super high in the priority, so I might get to this but not in the next 1-2 weeks.

@regro-cf-autotick-bot
Copy link
Contributor Author

I see that this PR has conflicts, and I'm the only committer. I'm going to close this PR and will make another one as appropriate. This was generated by

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants