




















Simply updating to GCC 16 solves the build failure:
diff --git a/PKGBUILD b/PKGBUILD
index c0e63ed..6b735d3 100755
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -5,7 +5,7 @@
pkgname=mipsel-linux-gnu-gcc
_pkgname=gcc
_target="mipsel-linux-gnu"
-pkgver=15.1.0
+pkgver=16.1.0
pkgrel=3
pkgdesc="The GNU Compiler Collection for the MIPS architecture"
url="https://www.gnu.org/software/gcc/"
@@ -16,8 +16,8 @@ makedepends=('gmp' 'mpfr')
options=('!ccache' '!distcc' '!emptydirs' '!libtool' '!strip')
source=(ftp://ftp.gnu.org/gnu/gcc/gcc-${pkgver}/${_pkgname}-${pkgver}.tar.xz{,.sig})
sha256sums=(
- 'e2b09ec21660f01fecffb715e0120265216943f038d0e48a9868713e54f06cea'
- '981a495a35fdc11e8f9762c2ebe93d250bbd6996618e8fe3d4ebb1f463df8ca9'
+ '50efb4d94c3397aff3b0d61a5abd748b4dd31d9d3f2ab7be05b171d36a510f79'
+ '33a851c045ea2ef6f580d82b2abfb1dc75d8b270727800028ca5f40c3b4a4246'
)
validpgpkeys=(
F3691687D867B81B51CE07D9BBE43771487328A9 # bpiotrowski@archlinux.org
NOTICE (Updated October 15 2021):
If you maintain scripts used to access ftp.gnu.org over FTP, we strongly encourage you to change them to use HTTPS instead.
Eventually we hope to shut down FTP protocol access, but plan to give notice here and other places for several months ahead of time. https://ftp.gnu.org/
Surely this advice should be followed and the package should be updated to use HTTPS?
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。
Dear @PolarianDev and @filmroellchen,
I have now updated the package to 16.1.0 upstream, and switched the sources to https. The gpg keys not actively used have been commented out.
Please let me know if you find any issues with it Kind regards
-effeffe