ARM OSX Migrator

[regro-cf-autotick-bot]

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://circleci.com/gh/regro/circle_worker/39950, please use this URL for debugging}

[conda-forge-linter]

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.

[isuruf]

cc @mattip. I guess there's no Apple silicon support yet.

[mattip]

@isuruf how can I help? I am not sure I understand what this is about.

[isuruf]

We are building packages for the new macOS arm64 platform. Does PyPy support that platform?

xref: https://en.wikipedia.org/wiki/Mac_transition_to_Apple_Silicon

[mattip]

Ahh, I see, there is a fail on macos with pypy. I think this is failing since it is looking for pypy but needs to find pypy3 instead? We don't currently package a symlink from pypy to pypy3, this will change with the next release

[mattip]

We support arm64 and support macos, so I am not sure what needs to change to get this going.

[isuruf]

There are ABI differences. https://developer.apple.com/library/archive/documentation/Xcode/Conceptual/iPhoneOSABIReference/Articles/ARM64FunctionCallingConventions.html#//apple_ref/doc/uid/TP40013702-SW1

[isuruf]

Btw, can pypy be cross-compiled?

[mattip]

Btw, can pypy be cross-compiled?

Not really. The platform python is probed for too many low-level things. Of course it could be done, but would require someone to push it.

[arigo]

@isuruf Can you check and confirm that the link you're pointing to also applies to the future macOS-on-arm64, and not only to iOS as written in it? Porting the calling convention inside PyPy's JIT to this standard looks like a quick job, but we cannot do it blindly. That is, I can do the porting quickly provided I have ssh access to a machine (or emulator).

[isuruf]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168#c7 seems to indicate that it applies to both iOS and macOS.

That is, I can do the porting quickly provided I have ssh access to a machine (or emulator).

Apple is shipping a developer transition kit (DTK), but I don't have access to one right now. @jjhelmus at Anaconda Inc does, but they have to check with legal about who they can share access with.

[mattip]

The failing job seems to be running on macOS 10.15.6 (19G73) from this image

[isuruf]

@mattip, yes, we've been cross-compiling for the new architecture.

[mattip]

OK, that covers the compilation, but how do you test?

[isuruf]

@mattip, Apple is shipping a Development Transition Kit to developers.

Closing the PR for now for the bot to move on and not block other recipes.

[isuruf]

@mattip, @arigo, what can we do here? @erykoff has access to the hardware, but due to the NDA, he can't give SSH access. He would be able to help out with testing though.

[mattip]

Some of the work to get the API differences sorted out might be able to be ported from the recent CFFI changes, but as @arigo says above, without access to the hardware he cannot be sure the JIT actually works.

[arigo]

As long as I have no ssh direct access, I can't do anything.