IMPORTANT: We are re-working the bootstrapping of the distro, but due to toxic
decisions made upstream at high level, the SDK seems to be now _really_
locked-in on some SDK related components using the complexity scam or bias.
Yes, there is some bits related to geopolitics and "control" of the software
needed for information systems of nearly any types. Much of this is planned
obsolescence based on the complexity scam->the technical trajectory is accutely
toxic.

XXX:In other word, upstream broke bootstrapping at a reasonable technical cost.
    We have to make decisions at our level, but everything is on hold because
    of the global crisis of the SARS-COV-2 virus.

----
This is as set of build scripts which bootstrap a kind of minimal/ultra-light
desktop gnu/linux distro (x86_64/AMD CPU and GCN GPU).

This is _our_ linux from scratch, our everyday distro (for AMD hardware,
but you can add all the supported others if you want to).
glibc is about to deprecate the support of libdl in static binaries. It seems
glibc and/or elf is becoming nasty (like gcc slowly turning into a piece of c++
crap like llvm). The goal was to get as many statically binaries as possible,
which is not a reasonable goal anymore due to kludgy and badly designed
software.

----
I have to recall this: due to glibc and gcc compiler driver limitations binaries
with modules (ELF dynamic shared libs) which use symbols from the latter, must
be built as dynamic elf binaries which export their symbols (--export-symbols
from the GNU ld). Such ELF objects cannot be built with a static glibc and the
gcc compiler driver. Additionaly, many other components were designed with the
"dynamic shared lib paradigm" in mind which will induce breakage if used from a
static library archive version.
----

The SDKs are brain damaged kludges: the only anti brain fuckage mitigation
approach would be to burn an hardcoded configuration for a gnu/linux system and
use some sh scripts to build the component from source (_always_ cross
compiling friendly).

Some components deployed by those scripts are personal forks of popular open
source components.

I publish those scripts because the knowledge they do contain may be of use by
the community in addition of the real linux-from-scratch.

notes:
    - you have reboot.S and poweroff.S in files/asm if you want to use those
      versions. Carefull, you don't have a sync syscall for your drive data.
    - some libraries are dynamic shared, though they could be static. This is
      to interface with close source binaries, games, because I'm a gamer,
      nobody is perfect.

-- 
Sylvain BERTRAND
sylvain.bertrand@legeek.net