aarch64 PR

[step21]

Checklist

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

[conda-forge-linter]

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) and found some lint.

Here's what I've got...

For recipe:

• Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

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

I do have some suggestions for making it better though...

For recipe:

• Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [11].
• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[step21]

@conda-forge-admin, please rerender

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

I do have some suggestions for making it better though...

For recipe:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

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

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• drone: passed
• travis: failed
• azure: passed

Thus the PR was not passing and not merged.

[isuruf]

@step21, tests are failing. Ping me once the tests pass and I'll merge.

[step21]

@isuruf I thought I had taken out ppc64le again, but apparently only locally. I was testing it on CI, but turns out it needs a much more extensive build as upstream does not provide a tarball for it, so everything has to be built from scratch and an existing ghc from yum or similar used for bootstrapping, so I decided to take it out, but apparently forgot to push.

[isuruf]

You can install using yum on CI by adding a yum_requirements.txt file to the recipe folder.

[step21]

thanks. I will just take much longer and probably take too long for CI, so I decided to take it out for now. Is it also possible to only use yum_requirements.txt for one arch?

[isuruf]

Is it also possible to only use yum_requirements.txt for one arch?

It's not at the moment.

I will just take much longer and probably take too long for CI, so I decided to take it out for now.

You can try cross-compiling from x86_64 to ppc64le