From 53a347eecc9af97057bd785ad0c89d1a2118c838 Mon Sep 17 00:00:00 2001
From: David P <megver83@parabola.nu>
Date: Wed, 17 Jun 2020 16:43:05 -0400
Subject: upgpkg: cross/cross-gcc 10.1.0-1

and add recommendations for a good pkgdesc

Signed-off-by: David P <megver83@parabola.nu>
---
 cross/cross-gcc/PKGBUILD | 27 +++++++++++++++++++++++----
 1 file changed, 23 insertions(+), 4 deletions(-)

(limited to 'cross/cross-gcc')

diff --git a/cross/cross-gcc/PKGBUILD b/cross/cross-gcc/PKGBUILD
index 279b64c6f..6fa116cca 100644
--- a/cross/cross-gcc/PKGBUILD
+++ b/cross/cross-gcc/PKGBUILD
@@ -68,7 +68,7 @@
 # < : experimental support. (future)
 
 #--------------------------------------------------------------------------------
-#  Tips for build():
+#  Tips for build()
 #--------------------------------------------------------------------------------
 # * If builing without "--disable-multilib" make sure to have "--with-python-dir=share/gcc-$_target"
 # 
@@ -76,11 +76,28 @@
 #   "--with-native-system-header-dir=/include". You'll also have to build and add a libc implementation
 #   in makedepends as $_target-<libc> (e.g. $_target-newlib or $_target-glibc)
 
+#--------------------------------------------------------------------------------
+#  Choosing the correct pkgdesc
+#--------------------------------------------------------------------------------
+# You must know wether your toolchain is a bare-metal one, if it's specifically for big-endian or
+# little-endian order and know its full name, if possible. Here are some useful tips:
+#
+# * If the toolchain has no operating system (see the toolchain triplet, <_os_target>), then it's a
+#   bare-metal toolchain, in which case you have to specify it in the pkgdesc
+# 
+# * Do a bit of research in forums, wikis and documents about the target you plan to build, a good
+#   idea is to see the description that other distros put (e.g. Debian) if they have the same toolchain
+#
+# Example: arm-linux-gnueabi-{gcc,binutils,$etc}
+# This toolchain has GNU/Linux as OS, so it's not a bare-metal one. It's for armel, which
+# stands for "ARM EABI little-endian", but the gnueabi part means it uses the GNU EABI. You can find
+# that info in Debian's gcc-arm-linux-gnueabi and a couple of FLOSS and programmers community forums.
+
 # Toolchain triplet: <_arch>-<machine>-<_os_target>
 # <machine> is generally optional and uneeded
 _target=x86_64-pc-linux-gnu
 
-# This are some options for names. Change $_target_name in pkgdesc according to the target architecture
+# This are some common options for names. Change $_target_name in pkgdesc according to the target architecture.
 case ${_target%%-*} in
     arm*) _target_name=ARM
     ;;
@@ -102,8 +119,10 @@ case ${_target%%-*} in
     ;;
 esac
 
+# Learn more about the correct package naming here:
+# https://wiki.archlinux.org/index.php/Cross-compiling_tools_package_guidelines#Package_naming
 pkgname=$_target-gcc
-_pkgver=9.3.0
+_pkgver=10.1.0
 #_snapshot=9-20190601
 pkgver=$_pkgver${_snapshot/*-/+}
 _islver=0.22
@@ -120,7 +139,7 @@ options=(!emptydirs !strip)
 source=(https://gcc.gnu.org/pub/gcc/releases/gcc-$_pkgver/gcc-$_pkgver.tar.xz
         #https://gcc.gnu.org/pub/gcc/snapshots/$_snapshot/gcc-$_snapshot.tar.xz
         http://isl.gforge.inria.fr/isl-$_islver.tar.bz2)
-sha512sums=('4b9e3639eef6e623747a22c37a904b4750c93b6da77cf3958d5047e9b5ebddb7eebe091cc16ca0a227c0ecbd2bf3b984b221130f269a97ee4cc18f9cf6c444de'
+sha512sums=('0cb2a74c793face751f42bc580960b00e2bfea785872a0a2155f1f1dbfaa248f9591b67f4322db0f096f8844aca9243bc02732bda106c3b6e43b02bb67eb3096'
             'fc2c9796979610dd51143dcefe4f5c989c4354571cc5a1fcc6b932fd41f42a54f6b43adfd289af61be7bd06f3a523fa6a7d7ee56680e32d8036beb4c188fa668')
 
 if [ -n "$_snapshot" ]; then
-- 
cgit v1.2.3