Apparently there is no reference to a .tmp_gas_check file or to a TOUT variable in Linux sources any more.
Bug: https://bugs.gentoo.org/75034#c14
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
eclass/linux-info.eclass | 6 ------
1 file changed, 6 deletions(-)
diff --git a/eclass/linux-info.eclass b/eclass/linux-info.eclass
index 9449a6359d2a..90982445fdab 100644
--- a/eclass/linux-info.eclass
+++ b/eclass/linux-info.eclass
@@ -170,12 +170,6 @@ KERNEL_DIR="${KERNEL_DIR:-${ROOT%/}/usr/src/linux}"
inherit toolchain-funcs
[[ ${EAPI} == 6 ]] && inherit eapi7-ver
-# bug #75034
-case ${ARCH} in
- ppc) BUILD_FIXES="${BUILD_FIXES} TOUT=${T}/.tmp_gas_check";;
- ppc64) BUILD_FIXES="${BUILD_FIXES} TOUT=${T}/.tmp_gas_check";;
-esac
On Tue, 02 Jul 2024, Ionen Wolkens wrote:
On a side-note, it was further a no-op for linux-mod-r1 which opted to intentionally ignore BUILD_FIXES (variable is currently read by kernel-2
and linux-mod-r0) and nobody complained.
If wanted, technically all references of BUILD_FIXES could probably be removed from eclasses given (normally) nothing sets that variable beside
that ppc workaround. It was also undocumented and more like a private variable.
Albeit some ebuilds (like the pre-linux-mod-r1 lttng-modules ebuild)
and users have wrongly used it, so it could break some spacebar heating.
No real need to bother with linux-mod.eclass either way given it's due
for eventual removal.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 475 |
Nodes: | 16 (2 / 14) |
Uptime: | 21:26:16 |
Calls: | 9,488 |
Calls today: | 7 |
Files: | 13,617 |
Messages: | 6,121,094 |