Hello Tom, Stephen,
Am 04.12.2017 um 20:02 schrieb Stephen Warren:
On 12/02/2017 06:12 PM, Tom Rini wrote:
Move the warning to an error as we have been promising would happen in this release.
Oh. This has broken my U-Boot build/test system. I guess it's entirely my fault for interpreting the "2018.01" warning as "you'll need to fix this in Jan 2018", not "you'll need to fix this as soon as development starts for 2018.01":-(
Yes, all my U-Boot tbot builds tonight failed :-(
I use eldk-5.8 (gcc 4.9.2) or I fetch toolchain with buildman from kernel org:
pollux:u-boot hs [ubi-rework] $ ./tools/buildman/buildman --fetch-arch arm
Downloading toolchain for arch 'arm' Checking: https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/ Downloading: https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/x86_64-gcc... Unpacking to: /home/hs/.buildman-toolchains Testing - looking in '/home/hs/.buildman-toolchains/gcc-4.9.0-nolibc/arm-unknown-linux-gnueabi/.' - looking in '/home/hs/.buildman-toolchains/gcc-4.9.0-nolibc/arm-unknown-linux-gnueabi/bin' - found '/home/hs/.buildman-toolchains/gcc-4.9.0-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc' - looking in '/home/hs/.buildman-toolchains/gcc-4.9.0-nolibc/arm-unknown-linux-gnueabi/usr/bin' Tool chain test: OK, arch='arm', priority 4 pollux:u-boot hs [ubi-rework] $
Which has gcc 4.9.0 ...
Is there a reason for requiring such an extremely new gcc, as opposed to simply something not ancient? For example, no LTS version of Ubuntu packages a compiler that's new enough to build U-Boot now:-(
bye, Heiko