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
21 lines
767 B
Diff
21 lines
767 B
Diff
SPDX-FileCopyrightText: 2023 fosslinux <fosslinux@aussies.space>
|
|
|
|
SPDX-License-Identifier: GPL-3.0-or-later
|
|
|
|
In GCC 10, fself-test is run on every GCC used in the
|
|
build process to ensure correctness. However this is not
|
|
yet introduced in GCC 4.7, so we no-op it.
|
|
|
|
--- gcc-4.7.4/gcc/common.opt 2023-01-23 21:22:23.630919284 +1100
|
|
+++ gcc-4.7.4/gcc/common.opt 2023-01-23 21:23:33.030143958 +1100
|
|
@@ -1701,6 +1701,10 @@
|
|
Common Report Var(flag_selective_scheduling2) Optimization
|
|
Run selective scheduling after reload
|
|
|
|
+fself-test=
|
|
+Common Undocumented Joined Var(flag_self_test)
|
|
+Run no-op self-tests.
|
|
+
|
|
fsel-sched-pipelining
|
|
Common Report Var(flag_sel_sched_pipelining) Init(0) Optimization
|
|
Perform software pipelining of inner loops during selective scheduling
|