[Buildroot] [PATCH v4 08/15] package/gcc: switch to gcc 8.x as the default

Arnout Vandecappelle arnout at mind.be
Tue Jun 25 22:25:59 UTC 2019



On 23/06/2019 18:21, Thomas Petazzoni wrote:
> Hello,
> 
> On Sun, 23 Jun 2019 00:35:38 +0200
> Romain Naour <romain.naour at gmail.com> wrote:
> 
>>> Arnout: do you still think gcc 4.9 is needed at this point ? If it is
>>> the case, should we keep gcc 4.9, but drop gcc 5 and 6 ?  
>>
>> Currently glibc >= 2.29 needs gcc >= 5 on all architectures.
>> So we can only build a toolchain with gcc 4.9 with uClibc and musl.
>> The upcoming release of glibc will require at least gcc 6.2 on all architectures
>> [1].
>>
>> If a toolchain with gcc 4.9 is really needed, it can be build with the 2019.02
>> LTS version.
> 
> So, Peter said for the next LTS (2020.02), we probably want to have
> removed the oldest gcc versions (4.9, 5 and 6, most likely).

 Yes indeed, we can't keep 4.9 around indefinitely, so let's drop it and 5 and 6
as well, leaving just the three most recent ones: 7, 8, 9.


>> Thomas, I have the same question about gdb 7.12.x.
> 
> I think we should also drop it. I was keeping it because it was the
> last gdb version that could be built with a toolchain that doesn't have
> C++11 support. But well, C++11 is there since gcc 4.8, so let's assume
> most sane people have moved their distribution to a version that has
> gcc 4.8 at least.
> 
> So on my side, green light to drop gdb 7.12.

 For gdb, does it actually make sense to keep multiple versions?

 Regards,
 Arnout




More information about the buildroot mailing list