gcc47

• Path: arch/adapted/gcc47
• 2026-07-15: build failure fixed, pkgrel 3 -> 2.1 (per this project’s adapted/ X.Y sub-versioning convention, see PKGREL_VS_PKGVER.md – initially bumped to a plain 4 in error, corrected by the user afterward; already published as 2.1). The 4 missing texinfo patches described below were never restored – instead, noticed package() already does rm -rf "${pkgdir}/usr/share/" right after install, so generated docs (infodir/mandir, both under /usr/share) never actually ship in the package regardless of whether makeinfo succeeds. Simplest fix: don’t generate docs at all rather than resurrect 4 missing patches for output that gets deleted anyway. Removed the 4 dangling patch references from source=()/md5sums=()/ sha256sums=()/prepare(), and added MAKEINFO=':' to the configure invocation in build()’s _conf array (a no-op instead of the real makeinfo).
• Also hit, separately: depends=() includes cloog, which only exists in this project’s own archlinuxaba repo, not official core/extra – so the plain extra-x86_64-build chroot (no private repo configured) can’t resolve it (error: target not found: cloog). Had to use scripts/archlinuxaba-x86_64-build instead (adds this project’s own repo to the chroot’s pacman.conf, see that script’s own header) – same reason repo_build.sh already uses it for x86_64 internally. If testing this package with a plain extra-x86_64-build by hand, remember it’ll fail for this reason alone, unrelated to any PKGBUILD bug.
• Test-built clean with scripts/archlinuxaba-x86_64-build (0 compiler errors; both gcc47 and gcc47-debug packages produced, ~10MB / 46MB). Built+signed+published to the private repo (x86_64).
• Known, not-yet-fixed issue (reported by the user, not investigated/fixed yet): after installing the package, a symlink is missing and has to be created manually: ln -s lib/libgcc_s.so.1 /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.4/libgcc_s.so. Presumably package() should be creating this itself (a versioned runtime-library symlink gcc’s own build normally sets up, or that a post-install hook should provide) but currently doesn’t. Next time this package is touched, add the equivalent ln -s to package() (or a .install post-install hook) and bump pkgrel.

Superseded (kept for context – the fix above addressed this)

• Build failure during the 2026-07-07 “build all packages for x86_64” private-repo release pass (see repo_release_logs/adapted_gcc47.log).
• PKGBUILD’s source=() array (lines 25-31) lists four local texinfo patch files that prepare() applies with patch -Nup1 -i "${srcdir}/<name>": gcc.texi.49.patch, 0000-sourcebuild.texi-itemx.patch, 0001-tm.texi-end-deftypevr.patch, 0002-invoke.texi-tie.patch. None of these four files actually exist in the package directory – only gcc-4.7.4-gcc-15-compilation.patch (a different, present patch) and the downloaded gcc-4.7.4.tar.bz2 are there. makepkg fails immediately at source retrieval: gcc.texi.49.patch was not found in the build directory and is not a URL.
• This is a genuine defect in the tracked package tree (missing local source files), not a build-environment or toolchain issue, and not something introduced by this release pass. Needs the four patch files restored (from wherever they were originally generated – the comment above the patch block says gcc.texi.49.patch was hand-generated via diff -pNau5 gcc/doc/gcc.texi{,.49}, so it may need regenerating rather than recovering from history) before this package can build again.
• Not fixed as part of the mass build pass – flagging only, since PKGBUILD repair (regenerating/sourcing 4 missing patches) is out of scope for a build+sign+publish run.