Commits on Source (3)
-
Oliver Smith authored
-
This can otherwise fail if the package was only built for some architectures so far, but not for the architecture that is being generated. E.g. right now musl-1.2.5-r6 was built already for x86_64 but not aarch64, which causes errors like the following when running "pmbootstrap aportgen musl-x86_64" on aarch64: >>> musl-x86_64: Fetching musl-1.2.5-r5-x86_64-edge.apk::http://dl-4.alpinelinux.org/alpine//edge/main/x86_64/musl-1.2.5-r5.apk Connecting to dl-4.alpinelinux.org (147.75.40.42:80) Connecting to dl-4.alpinelinux.org (147.75.40.42:443) wget: server returned error: HTTP/1.1 404 Not Found >>> ERROR: musl-x86_64: checksum failed
-
recent changes to the kernels build infra in -next seem to have exposed some issues with "pmbootstrap build --envkernel", specifically in the case where the APKBUILD doesn't build out-of-tree. We used to rely on the fact that the kernel output directory contains a Makefile which points to the source directory, however this Makefile now(?) contains an absolute path on the host, which won't match what's in the chroot. As a result, it's now necessary to build with the same output directory as the APKBUILD. We probably need some smarter code here... and/or more consistent APKBUILDs. Signed-off-by:
Caleb Connolly <caleb@postmarketos.org>
Showing
- pmb/aportgen/busybox_static.py 1 addition, 1 deletionpmb/aportgen/busybox_static.py
- pmb/aportgen/core.py 1 addition, 1 deletionpmb/aportgen/core.py
- pmb/aportgen/grub_efi.py 1 addition, 1 deletionpmb/aportgen/grub_efi.py
- pmb/aportgen/musl.py 1 addition, 1 deletionpmb/aportgen/musl.py
- pmb/build/envkernel.py 2 additions, 8 deletionspmb/build/envkernel.py
- pmb/config/__init__.py 1 addition, 0 deletionspmb/config/__init__.py