Switch arm64 and ppc64 builds to use Azure

[traversaro]

For some reason the arm64 and ppc64 build were not triggered after merging of #3 and #4, so I bumped the build number to make sure they are triggered.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[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.

[traversaro]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.

[traversaro]

Actually the problem is conda-forge/status#122 .

[traversaro]

Actually the problem is conda-forge/status#122 .

I guess we can simple switch to azure also for arm64 and ppc64 builds.

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

The emulated builds on arm64 and ppc64 take a lot of time (most of it spent in the configure script), but given that releases of diffutils are not this frequent I think it is reasonable compromise. @conda-forge/diffutils let me know if you have any objection, otherwise I think I can merge in one day.

[isuruf]

You can also do cross compiling by using conda-forge/status#122 (comment)

[traversaro]

You can also do cross compiling by using conda-forge/status#122 (comment)

Cool, I was not aware of this, thanks. I will try this as in any case there are no tests in this package.

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

And thanks for the fix @isuruf!

[traversaro]

Thanks to cross-compiling, the build time on arm64/ppc64 is reduced to ~5 minutes.

[traversaro]

I will try this as in any case there are no tests in this package.

Actually it seems that simple tests are there:

diffutils-feedstock/recipe/meta.yaml

Line 24 in 2e14a78

test:

. However, it seems that are executed anyhow, not sure how.

[isuruf]

However, it seems that are executed anyhow, not sure how.

Using QEMU

[traversaro]

However, it seems that are executed anyhow, not sure how.

Using QEMU

Great, then as long as the build system supports it, using cross-compiling seems to be always a better idea w.r.t. to emulation, as you still run tests while running a faster compilation. Thanks!

[traversaro]

However, it seems that are executed anyhow, not sure how.

Using QEMU

Great, then as long as the build system supports it, using cross-compiling seems to be always a better idea w.r.t. to emulation, as you still run tests while running a faster compilation.

Actually this is not completly true, as for some build systems (for example in C++/CMake) the tests normally need to run as part of the build step, and so they can't run if you are cross-compiling.