Arch Migrator

[regro-cf-autotick-bot]

This feedstock is being rebuilt as part of the aarch64/ppc64le migration.

Feel free to merge the PR if CI is all green, but please don't close it
without reaching out the the ARM migrators first at @conda-forge/arm-arch.

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. 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/12296054600 - please use this URL for debugging.}

[conda-forge-admin]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• ❌ This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12296230675. Examine the logs at this URL for more detail.}

[martin-g]

@gmatteo Why did you merge this PR ? Its CI checks didn't pass ...

I am trying to fix the build for ARM64 at #68 but it will take a while.

[gmatteo]

Oops, sorry, I hadn’t noticed that TRAVIS CI was failing. What should I do? Should I revert, or should I wait for your pull request?

[martin-g]

I am not sure how much time it will take me to make it work at AzureCI with cross-compilation...
The current issue is that ./configure runs some tests by compiling small code snippets to detect features and it fails due to cross-compilation: the binary is compiled for the target_platform (e.g. aarch64) but fails to be executed on the host (x86_64).
My current approach is to disable those mini checks in the .m4 files for cross-compilation. But there are many ...

If you don't revert the this PR then any new PR will also be red. I am not sure how much of an issue is this.

[gmatteo]

Abinit now also supports CMake, even though there’s still some work to be done. Do you think CMake is better than configure for supporting ARM64?

[martin-g]

I will have to test and see.

Is it possible to use a newer version of libxc ? At the moment the recipe says - libxc < 5 (

abinit-feedstock/recipe/meta.yaml

Line 40 in cba5829

- libxc <5.0

)
libxc 5.x feedstock added support for linux-aarch64
libxc 6.x adds support for osx-arm64 too

[gmatteo]

I'll let @mtorrent answer your question

[mtorrent]

Hi,
Yes you can use libxc up to version 6.2.
libxc 7 is likely to be OK but never tested with Abinit.