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]
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
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
Regenerate these aports, so the test case does not complain anymore
that they are outdated. Adds armv7 to the arch lines, as that is the
aportgen change which was done in pmbootstrap!1730.
Example: Building gcc-armhf for armhf does not make sense, so this
commit changes arch="all" to arch="aarch64 x86_64". This helps to
simplify the repository scripts (#970).
