Skip to content

Conversation

@regro-cf-autotick-bot
Copy link
Contributor

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

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented May 14, 2025

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.

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

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

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

@mattip
Copy link
Contributor

mattip commented May 15, 2025

On the aarch64 build I see an error when bazel building openssl, something about This system (linux-aarch64) is not supported. See file INSTALL for details..

On the ppc64le builds I see an error in resolving the conda build requirements

The following package could not be installed
└─ nodejs =22 * does not exist (perhaps a typo or a missing channel).

@jakirkham
Copy link
Member

@conda-forge-admin , please re-render

conda-forge-webservices[bot] and others added 3 commits May 15, 2025 07:06
* Rely on Bazel toolchain for common vars
* Specify Bazel toolchain in extras
* Use cross-compilation with Bazel
Comment on lines 17 to 28
source gen-bazel-toolchain
cat >> .bazelrc <<EOF
build --define CONDA_CC=${CC}
build --define CONDA_CFLAGS="${CFLAGS}"
build --define CONDA_AR=${AR}
build --define CONDA_NM=${NM}
build --define CONDA_RANLIB=${RANLIB}
build --define CONDA_SDKROOT=${SDKROOT}
# build --subcommands
build --crosstool_top=//bazel_toolchain:toolchain
build --cpu=${TARGET_CPU}
build --platforms=//bazel_toolchain:target_platform
build --host_platform=//bazel_toolchain:build_platform
build --extra_toolchains=//bazel_toolchain:cc_cf_toolchain
build --extra_toolchains=//bazel_toolchain:cc_cf_host_toolchain
build --toolchain_resolution_debug
build --define=with_cross_compiler_support=true
build --experimental_ui_max_stdouterr_bytes=16000000
build --local_ram_resources=HOST_RAM*.8 --local_cpu_resources=2
EOF
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Started with something more similar to Jax. Though some of those flags were redundant with bazel-toolchain. This can probably be tweaked further

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants