Please update PKGBUILD to not use any commit inside of the repo and instead use latest gcc (which is gcc 11 now)
-
add some patches or scripts like
fix_libtool_files.shorgcc-configure.patch/gcc-spec-env.patchfrom Gentoo -
use
_islver=0.22instead of 21 -
uncomment those lines:
# insist on dynamic linking, but keep static libraries because gnatmake complains
#mv "$pkgdir"/${_libdir}/adalib/libgna{rl,t}-${_majorver}.so "$pkgdir/usr/lib"
#ln -s libgnarl-${_majorver}.so "$pkgdir/usr/lib/libgnarl.so"
#ln -s libgnat-${_majorver}.so "$pkgdir/usr/lib/libgnat.so"
#rm -f "$pkgdir"/${_libdir}/adalib/libgna{rl,t}.so
#install -d "$pkgdir/usr/lib32/"
#mv "$pkgdir"/${_libdir}/32/adalib/libgna{rl,t}-${_majorver}.so "$pkgdir/usr/lib32"
#ln -s libgnarl-${_majorver}.so "$pkgdir/usr/lib32/libgnarl.so"
#ln -s libgnat-${_majorver}.so "$pkgdir/usr/lib32/libgnat.so"
#rm -f "$pkgdir"/${_libdir}/32/adalib/libgna{rl,t}.so
For me it compiled fine now and passed all tests required for installing those packages.
Will try to provide a .diff later so others can also compile it fine.
[user@archlinux ~]$ gcc --version
gcc (GCC) 11.0.0 20200503 (experimental)
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; the copy conditions are in the sources. It
gives NO guarantee; also not for MERCHANTABILITY or FOR SPECIAL PURPOSES.
[user@archlinux ~]$
Pinned Comments
jamespharvey20 commented on 2019-10-13 02:28
Temporarily hold to commit fcab78b9 (2019-10-01 18:21:31.) Otherwise, fails to build. There are several breaking commits after this, involving packaging failures on ada and a bootstrap failure when comparing stages 2 and 3.
jamespharvey20 commented on 2017-02-15 04:30
*** STICKY ***
These gcc*-git packages replace core's gcc* (non-git) packages. Technically, replacing the system gcc-libs can be dangerous. The possibility of a new upstream gcc git commit breaking your system isn't zero. When you compile and install this, you're using the latest git source, so you may be the first Arch user to be using that particular commit.
In practice, I haven't seen an Arch user report such a problem for many years. Just understand that if installing these packages causes your computer to eat you, don't have your loved ones blame me. Oh, and know that if things go wrong, all you *should* have to do is uninstall the git version and go back to a previously working git version or even the core version. You might be able to do this while your system is still running, or you might have to do something like boot off an Arch ISO CD.