mirror of
https://github.com/fosslinux/live-bootstrap.git
synced 2026-03-05 19:05:24 +01:00
6ed2e09f3a
- This idea originates from very early in the project and was, at the
time, a very easy way to categorise things.
- Now, it doesn't really make much sense - it is fairly arbitary, often
occuring when there is a change in kernel, but not from builder-hex0
to fiwix, and sysb is in reality completely unnecessary.
- In short, the sys* stuff is a bit of a mess that makes the project
more difficult to understand.
- This puts everything down into one folder and has a manifest file that
is used to generate the build scripts on the fly rather than using
coded scripts.
- This is created in the "seed" stage.
stage0-posix -- (calls) --> seed -- (generates) --> main steps
Alongside this change there are a variety of other smaller fixups to the
general structure of the live-bootstrap rootfs.
- Creating a rootfs has become much simpler and is defined as code in
go.sh. The new structure, for an about-to-be booted system, is
/
-- /steps (direct copy of steps/)
-- /distfiles (direct copy of distfiles/)
-- all files from seed/*
-- all files from seed/stage0-posix/*
- There is no longer such a thing as /usr/include/musl, this didn't
really make any sense, as musl is the final libc used. Rather, to
separate musl and mes, we have /usr/include/mes, which is much easier
to work with.
- This also makes mes easier to blow away later.
- A few things that weren't properly in packages have been changed;
checksum-transcriber, simple-patch, kexec-fiwix have all been given
fully qualified package names.
- Highly breaking change, scripts now exist in their package directory
but NOT WITH THE packagename.sh. Rather, they use pass1.sh, pass2.sh,
etc. This avoids manual definition of passes.
- Ditto with patches; default directory is patches, but then any patch
series specific to a pass are named patches-passX.
21 lines
747 B
Diff
21 lines
747 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/common.opt 2023-01-23 21:22:23.630919284 +1100
|
|
+++ 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
|