[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
howtos:hardware:arm:gcc-10.x_aarch64_cross-compiler [2021/04/22 12:41 (UTC)] – [Aarch64 cross-compiler script code] updated build script to use gcc-10.3.0 exagahowtos:hardware:arm:gcc-10.x_aarch64_cross-compiler [2021/10/01 09:26 (UTC)] (current) – [AArch64 cross-compiling 'HOWTO' example] removed superfluous text exaga
Line 1: Line 1:
 <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). -->
-====== Slackware ARM current gcc-10.2.x armv8 arm64 aarch64 cross-compiler for the Raspberry Pi 4 ======+====== Slackware ARM current gcc-10.3.x armv8 arm64 aarch64 cross-compiler for the Raspberry Pi 4 ======
  
 ===== Preface ===== ===== Preface =====
Line 10: Line 10:
 ===== Notes ===== ===== Notes =====
  
-Slackware ARM current was used on a Raspberry Pi 4 [4GB RAM] to build and install the gcc-10.2.0 aarch64-linux cross-compiler. +Slackware ARM current was used on a Raspberry Pi 4 [4GB RAM] to build and install the gcc-10.3.0 aarch64-linux cross-compiler. 
  
 The Linux kernel source downloaded is from the Raspberry Pi Github repository: https://github.com/raspberrypi/linux The Linux kernel source downloaded is from the Raspberry Pi Github repository: https://github.com/raspberrypi/linux
Line 27: Line 27:
 ===== Aarch64 cross-compiler script code ===== ===== Aarch64 cross-compiler script code =====
  
-Download the 'SARPi64.SlackBuild-gcc-10.2-aarch64-cc.sh' file by clicking the link at the top of the script code (or copy and paste the code if you prefer) below.+Download the 'SARPi64.SlackBuild-gcc-10.3-aarch64-cc.sh' file by clicking the link at the top of the script code (or copy and paste the code if you prefer) below.
  
-Make the file executable using 'chmod +x SARPi64.SlackBuild-gcc-10.2-aarch64-cc.sh' or 'chmod 755 SARPi64.SlackBuild-gcc-10.2-aarch64-cc.sh' command. +Make the file executable using 'chmod +x SARPi64.SlackBuild-gcc-10.3-aarch64-cc.sh' or 'chmod 755 SARPi64.SlackBuild-gcc-10.3-aarch64-cc.sh' command. 
  
 Refer to the commented top section of the script code for usage.  Refer to the commented top section of the script code for usage. 
Line 40: Line 40:
 # Slackware ARM gcc-10.3.0 aarch64 cross-compiler for Raspberry Pi # Slackware ARM gcc-10.3.0 aarch64 cross-compiler for Raspberry Pi
 # #
-# SARPi64.SlackBuild-gcc-10.3.0-aarch64-cc [v3.0] - 2020-04-22+# SARPi64.SlackBuild-gcc-10.3.0-aarch64-cc [v3.0] - 2021-04-22
 # #
 # 2020-12-29 by Exaga   -   v3.0   -  gcc-10.x # 2020-12-29 by Exaga   -   v3.0   -  gcc-10.x
Line 480: Line 480:
  
 # #
-# Compiler: aarch64-linux-gcc (GCC) 10.2.0+# Compiler: aarch64-linux-gcc (GCC) 10.3.0
 # #
 CONFIG_CC_IS_GCC=y CONFIG_CC_IS_GCC=y
-CONFIG_GCC_VERSION=100200+CONFIG_GCC_VERSION=100300
 root@slackware:/tmp/linux-rpi# </code> root@slackware:/tmp/linux-rpi# </code>
  
Line 501: Line 501:
 <note warning>**BEFORE CONTINUING - Make a back-up __FIRST__ of your '/boot/' directory before coping any new files to it, in case things don't go exactly as planned. Only reboot once everything is correctly in place and you have your backup(s) to fall-back on.**</note> <note warning>**BEFORE CONTINUING - Make a back-up __FIRST__ of your '/boot/' directory before coping any new files to it, in case things don't go exactly as planned. Only reboot once everything is correctly in place and you have your backup(s) to fall-back on.**</note>
  
-So with everything compiled and built, you just need to copy the 'kernel' image, 'DTBs' and 'System.map' to your '/boot' directory. Replace KERNEL_IMAGE with the correct filename of the kernel for your Raspberry Pi device:+So with everything compiled and built, you just need to copy the 'kernel' image, 'DTBs' and 'System.map' to your '/boot' directory.
  
-<note important>NB: For the RPi3 the kernel image is named 'kernel7.img' and for the RPi4 the kernel image is named 'kernel7l.img'. This filename __MUST__ be correct in order for the boot-loader to run the kernel! If you have specified a custom kernel image filename in the '/boot/config.txt' file then you already know what you're doing. ;-)</note>+<note important>NB: By default, on Raspberry Pi ARMv7 [32-bit] systems, the kernel image is named 'kernel7.img' on the RPi3, and for the RPi4 the kernel image is named 'kernel7l.img' - where the "L" is actually an indicator for "Large Physical Address Extension (LPAE)". However, on Raspberry Pi ARMv8 [64-bit] systems the kernel is named 'kernel8.img'. This filename __MUST__ be correct in order for the boot-loader to find and run the ARMv8 [64-bit] kernel! If you have specified a custom kernel image filename in the '/boot/config.txt' file then you already know what you're doing here. ;-)</note>
  
-<code>root@slackware:/tmp/linux-rpi# cp -avr arch/arm64/boot/Image /boot/KERNEL_IMAGE"+<code>root@slackware:/tmp/linux-rpi# cp -avr arch/arm64/boot/Image /boot/kernel8.img"
 root@slackware:/tmp/linux-rpi# cp -avr arch/arm64/boot/dts/broadcom/bcm27*.dtb /boot/ root@slackware:/tmp/linux-rpi# cp -avr arch/arm64/boot/dts/broadcom/bcm27*.dtb /boot/
 root@slackware:/tmp/linux-rpi# cp -avr System.map /boot/System.map</code> root@slackware:/tmp/linux-rpi# cp -avr System.map /boot/System.map</code>

Trace:

howtos:hardware:arm:gcc-10.x_aarch64_cross-compiler ()