On Wed, Dec 30, 2020 at 9:43 AM John Baldwin wrote:
>
> On 12/29/20 7:10 PM, Ryan Libby wrote:
> > I checked amd64 and it failed due to pkru. I don't think we care to fix
> > that either, but we technically could of course. For amd64 the external
> > toolchain with gcc 6.4 is broken at the momen
On Wed, Dec 30, 2020 at 3:33 AM Konstantin Belousov wrote:
>
> On Tue, Dec 29, 2020 at 07:10:02PM -0800, Ryan Libby wrote:
> > I checked amd64 and it failed due to pkru. I don't think we care to fix
> > that either, but we technically could of course. For amd64 the external
> > toolchain with gc
On Wed, Dec 30, 2020 at 09:43:50AM -0800, John Baldwin wrote:
> Just to be explicit, we do not care about building amd64 with 4.2.1 at this
> point on 12.x.
AFAIK the only use case for gcc4.2.1 is powerpc* < 13. (I check new
ports on powerpc64 vs. gcc4.2.1. I will be glad to see the end of it.)
On 12/29/20 7:10 PM, Ryan Libby wrote:
> I checked amd64 and it failed due to pkru. I don't think we care to fix
> that either, but we technically could of course. For amd64 the external
> toolchain with gcc 6.4 is broken at the moment but will be fixed after a
> few more MFCs.
Just to be explic
On Tue, Dec 29, 2020 at 07:10:02PM -0800, Ryan Libby wrote:
> I checked amd64 and it failed due to pkru. I don't think we care to fix
> that either, but we technically could of course. For amd64 the external
> toolchain with gcc 6.4 is broken at the moment but will be fixed after a
> few more MFC
