Make the version match Alpine's gcc again. Fixes libstdc++ unsatisfiable
constrains related error messages (because the libstdc++ generated by
these cross-* packages has the same pkgver and pkgrel again as the one
provided by Alpine's gcc package).
[ci:skip-build]
Use the native rustc cross compiler where possible, and fall back to the
qemu rustc if necessary. This should improve speed and reliability.
Without this patch, building squeekbox 1.4.0 for aarch64 with the
pmbootstrap stack just hangs forever.
Related: pmbootstrap#1861
The last update of the binutils-* pmaports were not made with the latest
pmbootstrap version, which has the additional empty line remved in the
generated aports. Fix this, so we get an empty diff when running
aportgen, unless the binutils version was changed in Alpine.
[ci:skip-build], [ci:skip-vercheck]
Rebuild all other GCC packages against mpfr4, so they don't fail with:
Error loading shared library libmpfr.so.4: No such file or directory (needed by /usr/gcc4/libexec/gcc/x86_64-alpine-linux-musl/4.9.2/cc1)
[ci:skip-build]: won't finish in time
Related: 2b32ed3a48786fa151cad8f920e5d9997bee94ed in Alpine's aports.git
Rebuild to make it use the new armhf triplet. Otherwise cross compiling
with crossdirect to armhf fails with:
ERROR: crossdirect: failed to execute /native/usr/lib/ccache/bin/armv6-alpine-linux-muslgnueabihf-gcc: No such file or directory
This finally fixes#295.
Rebuild to make it use the new armhf triplet. Otherwise cross compiling
with crossdirect to armhf fails with:
ccache: error: Could not find compiler "armv6-alpine-linux-muslgnueabihf-gcc" in PATH
Related: #295
Upgrading binutils-armhf was blocked, after the armhf triplet had been
renamed and gcc-armhf still had the old triplet. Now gcc-armhf was
upgraded. When trying to the upgraded build gcc-armhf with the current
set of binary packages, without updating binutils-armhf, it fails with:
configure: error: cannot compute suffix of object files: cannot compile
So let's upgrade binutils-armhf too and finally have the triplet of both
programs in sync again \o/
Related: #295
Make the version match Alpine's gcc again. Fixes libstdc++ unsatisfiable
constrains related error messages (because the libstdc++ generated by
these cross-* packages has the same pkgver and pkgrel again as the one
provided by Alpine's gcc package).
[ci:skip-build]: won't finish in time
The upstream compat test case will still fail after this, there are more
issues that need to be resolved. I'm on it.
Latest version from Alpine. I've checked that we can still compile
packages for armhf after this update, in other words that we don't get
a regression related to the triplet change like in #295.
This reverts commit 593fe01bb8.
Binaries in binutils-armhf etc. break the build system:
Error loading shared library libopcodes-2.32.so: Exec format error (needed by /usr/bin/as)
Error loading shared library libbfd-2.32.so: Exec format error (needed by /usr/bin/as)
Error loading shared library libz.so.1: Exec format error (needed by /usr/bin/as)
Error relocating /usr/bin/as: bfd_errmsg: symbol not found
Error relocating /usr/bin/as: deflateEnd: symbol not found
Error relocating /usr/bin/as: bfd_arch_bits_per_address: symbol not found
Error relocating /usr/bin/as: bfd_set_error_program_name: symbol not found
Error relocating /usr/bin/as: xcalloc: symbol not found
Reverting for now. The upstream compatibility CI test is expected to fail.
The postmarketOS binary repositories still have the old binutils package.
I'm analyzing this issue in #295.
[ci:skip-vercheck]: package downgrade
This package should use the pmb:strict option, in order to force
pmbootstrap to always build it in strict mode. Otherwise it can have
a conflict with packages installed earlier.
I've just noticed that the merged patch was still using the early name
of the option, "pmbootstrap-strict". It was later changed to
"pmb:strict" in the related pmbootstrap!1771 merge request, for
consistency with !pmb:kconfig-check. Fix grub-x86 to use the proper
option name.
[ci:skip-vercheck]: version bump not needed
Adjust the depends of the GCC-8 cross compiler packages after the change
from pmbootstrap!1778. This does not have any effect (since the GCC-8
aports don't have !tracedeps in options, in contrary to the other GCC
aports we ship). But it makes sure that we don't get any changes after
running the repository maintenance script from here:
https://wiki.postmarketos.org/wiki/Repository_maintenance
[ci:skip-build]: cosmetic change, build would take too long anyway
Oliver Smith