i686-elf-pcc-git
- Path: arch/maintained/i686-elf-pcc-git
- Build failure during the 2026-07-07 “build all packages for x86_64”
private-repo release pass (see
repo_release_logs/maintained_i686-elf-pcc-git.log).
- Same systemic intra-tree dependency-ordering gap: needs
i686-elf-pcc-libs (built from maintained/i686-elf-pcc-libs-git,
alphabetically after this package so not yet published) and
i686-elf-binutils (from maintained/i686-elf-binutils, which did
already pass earlier in this same run, just moments before this
package was attempted – so that half should already resolve on
retry).
- Should resolve on a retry once
i686-elf-pcc-libs-git is
built+published too. Not retried yet as part of this pass.
- 2026-08-02: retried after publishing
i686-elf-pcc-libs-git
(20260208-1). x86_64 built+published cleanly (20260707-1, +
i686-elf-pcc-git-debug).
- i686 still fails, but for a different reason than the ordering gap
above:
target not found: i686-elf-pcc-libs / i686-elf-binutils,
even though both are published to archlinuxaba and resolve fine
for x86_64. Root cause: stock extra-i686-build doesn’t have the
archlinuxaba repo in its pacman.conf at all (only the x86_64
wrapper, scripts/archlinuxaba-x86_64-build, does – see
repo_build.sh’s own header comment, “Every other arch still uses
stock extra--build for now”). This is a pre-existing systemic
gap in the build tooling, not a packaging bug – any package on a
non-x86_64 arch depending on another privately-published package
will hit the same wall. Not fixed here (would mean adding
archlinuxaba to every arch’s devtools pacman.conf.d, a tooling-level
change out of scope for a single package). x86_64 publish is the
practical result for now.
- Also independently hit one transient
mirror.archlinux32.org connection timeout on an earlier retry –
unrelated flake, resolved by just retrying.