Slarm64-15.0 trusted-firmware-a-master aarch64-none-elf-gcc
by Stragonian from LinuxQuestions.org on (#6KEYP)
Greetings Slarm64 community, I have been attempting to build the trusted-firmware-a-master from a default Slarm64-15.0 install, running on a Banana Pi M64.
Compile instruction can be found here ....
https://trustedfirmware-a.readthedoc...allwinner.html
When I attempt to compile the firmware using the instruction from the website, I get:
Code:export BL31=$(pwd)/build/sun50i_a64/debug/bl31.bin
make PLAT=sun50i_a64 DEBUG=1 bl31
/bin/sh: line 1: aarch64-none-elf-gcc: command not foundThe compile immediately produces the above error ...
All the online pre-packaged aarch64-none-elf-gcc compilers I have found for native Aarch64 systems, are all built from different glibc, so the Slarm64-15.0 system fails to use them successfully. So, now I am left with some question ....
First, what is the difference between the aarch64-slackware-linux-gcc and the aarch64-none-elf-gcc?
Second, Is there a workaround, so I can use the aarch64-slackware-linux-gcc which is already installed in the system rather than an aarch64-none-elf-gcc to compile the trusted-firmware-a-master?
Third, would building an aarch64-none-elf-gcc for slarm64-15.0 and Slackware-current Aarch64 be beneficial for Slackware Arm's & Aarch64's further development? ( Since the trusted-firmware-a-master used by u-boot for Arm / Aarch64 depends on an aarch64-none-elf-gcc compiler )
Fourth, do I need to compile my own aarch64-none-elf-gcc compiler from the gcc-11.2.0 source with ./configure --target=aarch64-none-elf?
Fifth, How would I go about compiling my own aarch64-none-elf-gcc compile if it is more complicated than just ./configure --target=aarch64-none-elf?
Anyway, I'm not sure if this is more of the whole cross-compiling nightmare of using an Arm32/Arm64 systems or not.
Plus: Why do some many build scripts from github assume I am cross-compiling from a x86_64 system?
Compile instruction can be found here ....
https://trustedfirmware-a.readthedoc...allwinner.html
When I attempt to compile the firmware using the instruction from the website, I get:
Code:export BL31=$(pwd)/build/sun50i_a64/debug/bl31.bin
make PLAT=sun50i_a64 DEBUG=1 bl31
/bin/sh: line 1: aarch64-none-elf-gcc: command not foundThe compile immediately produces the above error ...
All the online pre-packaged aarch64-none-elf-gcc compilers I have found for native Aarch64 systems, are all built from different glibc, so the Slarm64-15.0 system fails to use them successfully. So, now I am left with some question ....
First, what is the difference between the aarch64-slackware-linux-gcc and the aarch64-none-elf-gcc?
Second, Is there a workaround, so I can use the aarch64-slackware-linux-gcc which is already installed in the system rather than an aarch64-none-elf-gcc to compile the trusted-firmware-a-master?
Third, would building an aarch64-none-elf-gcc for slarm64-15.0 and Slackware-current Aarch64 be beneficial for Slackware Arm's & Aarch64's further development? ( Since the trusted-firmware-a-master used by u-boot for Arm / Aarch64 depends on an aarch64-none-elf-gcc compiler )
Fourth, do I need to compile my own aarch64-none-elf-gcc compiler from the gcc-11.2.0 source with ./configure --target=aarch64-none-elf?
Fifth, How would I go about compiling my own aarch64-none-elf-gcc compile if it is more complicated than just ./configure --target=aarch64-none-elf?
Anyway, I'm not sure if this is more of the whole cross-compiling nightmare of using an Arm32/Arm64 systems or not.
Plus: Why do some many build scripts from github assume I am cross-compiling from a x86_64 system?