On Mon, Dec 04, 2017 at 12:02:20PM -0700, Stephen Warren wrote: > 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":-(
I'm tagging v2018.01-rc1 later today, so I think this is about the time to enforce the warning. > 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:-( There's always the Free Electrons toolchains, as well as Linaro. And yes, we've been having size problems and having to play various games to allow for older gcc versions to still fit things in. GCC-6 is where https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54303 was resolved and we get a lot of space saved, and a number of platforms simply won't work with older. -- Tom
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
