Skip to content
coders.talk
PidebugDevOps1 file · +2 −2

Fix conda-forge bazel-feedstock linux-aarch64 build failure

Session from conda-forge-agent-traces on Hugging Face by xhochy · BSD-3-Clause · condensed by Coders Talk

21msession
0interventions
by library · 1d
conda-forgebazelconda-smithyBashconda-build
GOAL

Diagnose and fix a failing conda-build for the bazel-feedstock on linux-aarch64, using the conda-forge skill and web research to identify the root cause.

  1. Prompt · +0
    conda-build failed on linux-aarch64 for bazel-feedstock; use the conda-forge skill and web search to find and fix similar issues, starting by reproducing the error.
  2. Agent did · +0m
    Loaded the conda-forge skill, inspected the feedstock's recipe, meta.yaml, and linux_aarch64 CI config to understand the build setup.
  3. Agent did · +1m
    Ran the failing conda-build command and captured the error output showing a failure inside the cc_toolchain_config apply_cc_template step.
  4. Fail · +2m
    Build failed with an error while applying the cc toolchain template, tied to sed processing of version variables.
  5. Agent did · +4m
    Read build.sh, tried to inspect the conda-bld environment's package list to check ABSEIL_VERSION/PROTOC_VERSION extraction, hitting missing conda/python binaries before finding pixi exec worked.
  6. Agent did · +6m
    Web-searched for similar bazel-feedstock aarch64 build failures, checked the libprotobuf-bazel-systemlib feedstock repo and git history, and located the ABSEIL_VERSION/PROTOC_VERSION extraction lines in build.sh using conda list substring matching.
  7. Agent did · +11m
    Edited recipe/build.sh to quote and properly filter the ABSEIL_VERSION and PROTOC_VERSION conda list output so systemlib packages with similar names don't produce duplicate multi-line version strings.
  8. Agent did · +16m
    Re-ran the full conda-build for linux_aarch64 with the fix applied; build completed successfully this time.
  9. Agent did · +20m
    Committed the build.sh fix, re-rendered the feedstock with conda-smithy, and confirmed linting passes cleanly.
  10. Outcome · +21m
    Root cause identified: duplicate libabseil/libprotobuf systemlib packages broke version extraction via sed; fix committed (06563a8), feedstock re-rendered, conda-build now succeeds and lint passes.
VERDICT

Next time I'd start by dumping the installed packages in the build prefix earlier, since the duplicate systemlib packages were the actual root cause and cost a lot of back-and-forth with conda/python/pixi path issues. The web search pointing to the libprotobuf-bazel-systemlib feedstock was what actually cracked it open - once I saw the substring-matching problem, the build.sh fix was quick and the rebuild confirmed it.

I tried this · 0

Discussion · 0

How Builds work