Build for linux-ppc64le

[agriyakhetarpal]

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.

[agriyakhetarpal]

@conda-forge-admin, please rerender

[conda-forge-admin]

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/meta.yaml) and found it was in an excellent condition.

[agriyakhetarpal]

I don't have full access to a computer right now, so this PR has been created from GitHub's web interface. I've triggered a rerender of the feedstock in the meantime and I can dive into any errors that arise with the compilation (I expect a few) in a while.

Edit: I've re-rendered locally with edd91c3.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub actions workflow below for more details. You can also ping conda-forge/core for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

• Is the recipe/{meta.yaml,recipe.yaml} file valid?
• If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
• Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11314779755.}

[agriyakhetarpal]

sed: can't read /home/conda/feedstock_root/build_artifacts/zig_1728828681553/_build_env/ppc64le-conda-linux-gnu/sysroot/usr/lib64/libm.so: No such file or directory should be fixed if I set SYSROOT_ARCH as powerpc64le instead of ppc64le.

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

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [50, 54]

[conda-forge-admin]

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/meta.yaml) and found it was in an excellent condition.

[agriyakhetarpal]

I see that y'all have tried this already 😁 cross-linking to ziglang/zig#20335, and to #25 (comment) for me to refer further. ziglang/zig-bootstrap#113 (comment) mentions that we need ziglang/zig#17749.

ziglang/zig#21650 and ziglang/zig#21651 discuss further support for this target, and essentially the blocker here is ziglang/zig#5927. I don't think we should support ELF v1 since Zig will support just v2 in the next release – ziglang/zig#21310 was just merged. So, we'll need some of those other issues to move further – I can rebase this PR then.

In the meantime, I'll continue to rely on https://github.com/ziglang/zig-pypi/ which can repackage the official ppc64le builds for me as wheels :)

Side note: has the usage of those wheels to build a no-arch conda package here been discussed before? It would need a patch to expose the zig entry point in the system's PATH, but that should all work. never mind, that would add a dependence on Python, which, strictly speaking, the "language" does not need :P