mirror of
https://github.com/fosslinux/live-bootstrap.git
synced 2026-03-02 01:18:08 +01:00
a67db8fcbd
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
23 lines
792 B
Diff
23 lines
792 B
Diff
SPDX-FileCopyrightText: 2021 fosslinux <fosslinux@aussies.space>
|
|
|
|
SPDX-License-Identifier: GPL-2.0-only
|
|
|
|
kconfig uses gperf, which we don't have at this stage. We manually generate
|
|
everything (in the actual script) that is actually required within kconfig,
|
|
and forgo everything that is not really required for the build.
|
|
|
|
--- linux-4.14.336/Makefile 2021-07-30 21:25:43.577592065 +1000
|
|
+++ linux-4.14.336/Makefile 2021-07-30 21:26:40.349015612 +1000
|
|
@@ -547,10 +547,10 @@
|
|
export KBUILD_DEFCONFIG KBUILD_KCONFIG
|
|
|
|
config: scripts_basic outputmakefile FORCE
|
|
- $(Q)$(MAKE) $(build)=scripts/kconfig $@
|
|
+ $(Q)true
|
|
|
|
%config: scripts_basic outputmakefile FORCE
|
|
- $(Q)$(MAKE) $(build)=scripts/kconfig $@
|
|
+ true
|
|
|
|
else
|
|
# ===========================================================================
|