The _SUPPORTS option should be blind: it represents a restriction that
we certainly do not want to allow the user to lift by manually enabling
that option...
Fixes: 65f268e21c (package/arm-gnu-toolchain: add
BR2_PACKAGE_HOST_ARM_GNU_TOOLCHAIN_SUPPORTS)
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: Bryce Johnson <bryce@redpinelabs.com>
Cc: Suniel Mahesh <sunil@amarulasolutions.com>
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Julien Olivain <ju.o@free.fr>
ARM gnu toolchain for bare metal arm32 target is only available for
x86_64 and aarch64 hosts. Introduce a new option to disable packages
using this toolchain on unsupported hosts.
[Romain: improve commit log]
Signed-off-by: Bryce Johnson <bryce@redpinelabs.com>
Signed-off-by: Romain Naour <romain.naour@smile.fr>
When building on an ARM64 build server, the build of
configs/ti_am62x_sk_defconfig fails when building the Cortex-R5
U-Boot, as it uses host-arm-gnu-toolchain, which assumes the host
machine is x86-64.
Use $(HOSTARCH) instead so that it can download the bare-metal
toolchain also provided by ARM for the ARM64 host architecture.
Signed-off-by: Bryce Johnson <bryce@redpinelabs.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The arm-gnu-toolchain is used by TI's K3 generation of devices to
compile the first stage bootloader (tiboot3.bin) which will run on the
32bit R5 MCU.
The 10.3-2021.10 version of this toolchain is no longer publicized as
being downloadable (and it's fairly old) on ARM's website. Let's upgrade
to the latest version of the toolchain ARM (13.2-rel1)
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Revert the toolchain to version 10.x because of bug in 11.x:
when the pre-packaged GCC was built, it could be targeting
a newer x86_64 architecture than the processor being used.
Confirmed fix will be implemented in the next release:
https://bugs.linaro.org/show_bug.cgi?id=5825#c19
Signed-off-by: Xuanhao Shi <x-shi@ti.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
It's time to finally switch over globally to the new spacing format
that we have agreed on for the hash file, with 2 spaces as a separator
between fields.
This commit was mechanically generated using:
find . -type f -name '*.hash' | xargs sed -i 's%^md5[ \t]*\([^ \t]*\)[ \t]*\(.*\)$%md5 \1 \2%'
find . -type f -name '*.hash' | xargs sed -i 's%^sha1[ \t]*\([^ \t]*\)[ \t]*\(.*\)$%sha1 \1 \2%'
find . -type f -name '*.hash' | xargs sed -i 's%^sha256[ \t]*\([^ \t]*\)[ \t]*\(.*\)$%sha256 \1 \2%'
find . -type f -name '*.hash' | xargs sed -i 's%^sha512[ \t]*\([^ \t]*\)[ \t]*\(.*\)$%sha512 \1 \2%'
This commit can easily be backported on the LTS branch by re-running
the same commands, if needed.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Yann E. MORIN