Diff glibc-2.43-r4 with a glibc-2.43-r6

/usr/portage/sys-libs/glibc/glibc-2.43-r6.ebuild 2026-10-20 20:01:06.438810226 +0300
12 12
EMULTILIB_PKG="true"
13 13

  
14 14
# Gentoo patchset (ignored for live ebuilds)
15
PATCH_VER=5
15
PATCH_VER=7
16 16

  
17 17
# gcc mulitilib bootstrap files version
18 18
GCC_BOOTSTRAP_VER=20201208
......
42 42
if [[ ${PV} == *9999 ]]; then
43 43
	inherit git-r3
44 44
else
45
	KEYWORDS="~alpha amd64 arm arm64 ~hppa ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 ~sparc x86"
45
	KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
46 46
	SRC_URI="mirror://gnu/glibc/${P}.tar.xz"
47 47
	SRC_URI+=" https://distfiles.gentoo.org/pub/proj/toolchain/glibc/patches/${P}-patches-${PATCH_VER}.tar.xz"
48 48
	SRC_URI+=" verify-sig? ( mirror://gnu/glibc/${P}.tar.xz.sig )"
......
1755 1755
#
1756 1756
# If coreutils is built with USE=multicall, some of these files
1757 1757
# will just be wrapper scripts, not actual ELFs we can test.
1758
#
1759
# We allow to skip this sanity check, as insane as that may seem.
1760
# The one use-case I know of is changing the main ABI in-place;
1761
# the test runs existing binaries against the default ld.so, which
1762
# fails then, while the binaries should be executable just fine
1763
# using one of the other multilib variants that we install.
1764
#
1758 1765
glibc_sanity_check() {
1766
	if [[ ${I_ALLOW_TO_BREAK_MY_SYSTEM} = yes ]] ; then
1767
		ewarn "Skipping glibc sanity tests. You have been warned. Last 5s to abort."
1768
		sleep 5
1769
	else
1770

  
1759 1771
	cd / #228809
1760 1772

  
1761 1773
	# We enter ${ED} so to avoid trouble if the path contains
......
1790 1802
	done
1791 1803

  
1792 1804
	popd >/dev/null
1805

  
1806
	fi
1793 1807
}
1794 1808

  
1795 1809
pkg_preinst() {
Thank you!