Should we have a 2.30.1 point release ?
Jeff Law
law@redhat.com
Fri Apr 20 15:00:00 GMT 2018
On 04/20/2018 08:55 AM, Carlos O'Donell wrote:
> On 04/20/2018 05:51 AM, Nick Clifton wrote:
>> Hi Catherine,
>>
>>> What date are you targeting for the next major release?
>>
>> July 2018. (I am hoping to make 2 releases per year).
>
> A month before the glibc 2.28 release in August 2018...
> how fortuitous! Would you like to coordinate so we test the
> new glibc with the latest binutils?
:-) My tester will do that automatically.
For targets where we can build natively or pseudo-native with qemu it does:
1. Build and install binutils trunk
2. Bootstrap & install gcc trunk
3. Build glibc with just installed tools
4. Build kernel with just installed tools
For other *-linux-gnu targets where we can't exploit qemu's ability to
do dynamic translation:
1. Build and install binutils trunk as cross
2. Build and install gcc trunk as cross
3. Build glibc with cross tools
4. Build kernel with cross tools
I don't test as many sub-configs as build-many-glibcs. But for various
oddball targets the builds appear native (hppa, m68k, various arm
things, etc). So on those targets it's doing a deeper level of build
testing.
Jeff
More information about the Binutils
mailing list