search

conda-forge / basemap-feedstock

A conda-smithy repository for basemap.
BSD 3-Clause "New" or "Revised" License
10 stars 12 forks source link

ARM OSX Migrator #111

Closed regro-cf-autotick-bot closed 1 year ago

regro-cf-autotick-bot commented 1 year ago

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 code>@<space/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. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/4270265604, please use this URL for debugging.

conda-forge-webservices[bot] commented 1 year ago

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.

ReimarBauer commented 1 year ago

@molinav I'm not sure if a conda smithy rerender is missing. Unfortunately I don't have a M1++ System.

molinav commented 1 year ago

@ReimarBauer I have rerendered recently when adding the support for Python 3.11, I will need to check deeper where the issue is coming from.

molinav commented 1 year ago

@ReimarBauer It seems that the problem comes from the fact that the M1 packages have to be built with cross-compilation, and for some reason the script complains about an incompatible Python binary being chosen:

[...]/bin/python: Bad CPU type in executable

I need to investigate a bit further.

molinav commented 1 year ago

So it seems that the Python binary problem was not in the basemap subrecipe, but it occured when trying to build basemap-data and basemap-data-hires in the cross-compiling jobs.

For the moment, I have disabled basemap-data and basemap-data-hires in these cross-compiling situations, but it is something that needs a fix, because otherwise these pipelines may have problems when the basemap-data and basemap-data-hires versions are bumped.

molinav commented 1 year ago

This PR should not be merged yet. Because of adding the build skip to basemap-data and basemap-data-hires, these packages are now being created as specific for a given target platform, when they should be noarch packages. It can also be seen in the fact that the data packages get different hash depending if they were built on Windows, GNU/Linux or MacOS.

molinav commented 1 year ago

Still I cannot make it work. I cannot use the skip option on the data packages because they stop being noarch: python packages, but keeping it as now throws the "Bad CPU type" error when building the data packages.

molinav commented 1 year ago

@conda-forge-admin please rerun bot

regro-cf-autotick-bot commented 1 year ago

Due to the bot-rerun label I'm closing this PR. I will make another one as appropriate. This was generated by https://github.com/regro/cf-scripts/actions/runs/5650571687