Support ppc64le and fix cross architecture bootstrapping
- Nov 25, 2024
-
-
Jens Reidel authored
Signed-off-by:
Jens Reidel <adrian@travitia.xyz>
-
Jens Reidel authored
pmbootstrap qemu did not respect architecture-specfic QEMU command name mappings. Signed-off-by:
Jens Reidel <adrian@travitia.xyz>
-
Jens Reidel authored
Signed-off-by:
Jens Reidel <adrian@travitia.xyz>
-
Jens Reidel authored
Previously, it would only fall back to parsing all APKBUILDs if a main package was guessed for this potential subpackage. We do however want to scan all APKBUILDs in case the package is provided by one of the packages in pmaports. Signed-off-by:
Jens Reidel <adrian@travitia.xyz>
-
Jens Reidel authored
Signed-off-by:
Jens Reidel <adrian@travitia.xyz>
-
Jens Reidel authored
g++ is a subpackage of gcc, but cannot be detected as such easily by pmbootstrap. This is because g++ is not gcc-g++ or any other variant of such package names. Similarly, the detection for musl-dev-ppc64le and other architectures is broken, since the -dev suffix detection does not work if there is an architecture suffix. To fix it, add special case handling for cross toolchain and packages and have that fixup the -dev cases and hardcode g++ as a subpackage of gcc. To reproduce: - Generate ppc64le cross packages: pmbootstrap aportgen gcc-ppc64le musl-ppc64le - Build a package (to trigger building cross compilers): pmbootstrap build hello-world --arch=ppc64le Signed-off-by:
Jens Reidel <adrian@travitia.xyz>
-
Jens Reidel authored
self.arch is a property and calls Arch.from_str, which errors upon encountering an unknown architecture. Therefore, the error message is changed and needs to be adjusted in the tests. Since Arch.supported is a set, error messages were not deterministic before, so we need to sort the list of architectures now. Signed-off-by:
Jens Reidel <adrian@travitia.xyz>
-
Jens Reidel authored
riscv64 is supported but currently not covered by the arch test suite. Signed-off-by:
Jens Reidel <adrian@travitia.xyz>
-