live-bootstrap/steps/linux-4.14.341-openela/patches/disable-broken-check.patch
fosslinux a67db8fcbd Make patches relative to where tarballs are extracted
Ever since an old patch version, it has (for reasonable security
reasons) not supported patched with ../ in the filename.
Many of our patches have been relying on this behaviour being OK,
because we start off with an ancient patch version that didn't perform
such checks. As soon as we need this behaviour after we build a newer
patch though, we will have problems.

So, let's change the policy.
Patches are relative to where tarballs are extracted, rather than the
"working directory" - e.g. have patches for `coreutils-9.4/src/cp.c`
instead of `src/cp.c`.
Keeping this consistent has a few implications;
- patches are applied from the build/ directory in bash era now, with
  `-p0`
- when patches are manually applied in the bash era, use `-p` as
  required, usually `-p1`
- in kaem era where patches are always manually applied, `-p1` is used
2024-12-23 15:20:42 +11:00

22 lines
790 B
Diff

SPDX-FileCopyrightText: 2021 fosslinux <fosslinux@aussies.space>
SPDX-License-Identifier: GPL-2.0-only
There's something incorrect with this macro for live-bootstrap, most likely as
a result of the dodgy installation of linux-headers. However, there is no
problem with this, and it is verified that BITS_PER_LONG __BITS_PER_LONG
have functional and correct values.
--- linux-4.14.336/tools/include/asm-generic/bitsperlong.h 2021-07-31 11:50:26.616768608 +1000
+++ linux-4.14.336/tools/include/asm-generic/bitsperlong.h 2021-07-31 11:50:36.786847443 +1000
@@ -9,10 +9,6 @@
#define BITS_PER_LONG __WORDSIZE
#endif
-#if BITS_PER_LONG != __BITS_PER_LONG
-#error Inconsistent word size. Check asm/bitsperlong.h
-#endif
-
#ifndef BITS_PER_LONG_LONG
#define BITS_PER_LONG_LONG 64
#endif