lbmk.git/script/trees, branch 20241206rev9

set up python in PATH, ensuring that it is python3

2025-01-05T21:48:45+00:00

we already check the python version, and set a variable
for it, so that we can reliably use python3, even if
python in PATH doesn't correspond to python3. for
example if a system has python as python2 and python3
as python3

well, we use that when running deguard for example, but
various upstream projects that we use may need python,
and all of them use python3, not 2

so, re-use the python variable set up by lbmk, and
set it up in PATH accordingly. this now makes the note
about python3 obsolete, on docs/build.md in lbwww.git

Signed-off-by: Leah Rowe

update my copyright years on modified scripts

2025-01-03T18:09:03+00:00

there are some lbmk scripts that i modified, starting
this year. update the headers.

Signed-off-by: Leah Rowe

Revert "fix more unescaped quotes in eval"

2025-01-03T15:56:41+00:00

This reverts commit ec6bcc1fba5fbdf8b19b3d1cf9711f3d4c9c3741.

fix more unescaped quotes in eval

2025-01-03T15:43:27+00:00

it should fix more build errors that might have appeared
in the aforementioned revision, mentioned in the previous
commit message

Signed-off-by: Leah Rowe

fix lbmk shellcheck errors

2025-01-02T23:52:45+00:00

There was also a condition in run_make_command that is now
an OR, where it was an AND, on script/trees, to fix the use
of mixed (and erroneous) OR/AND operators.

I'm planning a much more invasive audit than this. These are
light fixes, intended for Libreboot 20241206 rev8.

Signed-off-by: Leah Rowe

move xbmkpath to XBMK_CACHE/

2024-12-30T21:25:55+00:00

When doing ./mk release, the build system would create
symlinks inside xbmkpath/ relative to the current work tree,
which will differ from what's in PATH.

Since XBMK_CACHE is already set globally, from the main work
tree and the release-build work tree, that means we can know
reliably that PATH is always correct if we put xbmkpath/
inside XBMK_CACHE.

Signed-off-by: Leah Rowe

Revert "Remove legacy update/vendor commands"

2024-12-30T21:06:05+00:00

This reverts commit 781320514623653077cda2d910b9baf150949bd1.

I'm doing changes for 20241206 rev8. It was a mistake to
remove these; they will be removed again, after rev8.

The documentation standardised on ./mk a while ago now, and
it's almost time to remove these commands. However, anyone
using the old commands ought to be able to, up to and including
any revision of the Libreboot 20241206 release.

It is my intention that these legacy commands finally be
removed for the next testing release, as part of a much wider
build system audit that I'm doing between now and then.

(Libreboot Build System Audit 7 is underway, and several of
these early audit7 changes are going on 20241206 rev8; after
that, I will create a branch named 20241206_branch off of rev8,
and anything in master from then on will contain much wilder
changes, with more conservative changes in 20241206_branch)

Signed-off-by: Leah Rowe

trees: remove unnecessary subshell

2024-12-30T18:38:42+00:00

Signed-off-by: Leah Rowe

trees: only symlink host gcc/gnat to build xgcc

2024-12-30T18:36:46+00:00

In general, we don't want to mess with the hostcc, unless
we have to. To avoid other breakage, clear what we did
after crossgcc has compiled.

This is a follow-up to the previous patches, matching gcc
to gnat versions and vice versa, when compiling crossgcc.

Signed-off-by: Leah Rowe

trees: correction on check_gnu_path

2024-12-30T17:59:19+00:00

i intend for this function to work generically,
matching gnat to gcc or gcc to gnat, but there was
a hangover from the previous code where it specifically
assumed we were matching gnat

this bug manifested when i tested with gnat being v13
and gcc being v14 in path, where gcc-13 was also
available in path.

Signed-off-by: Leah Rowe