Re: Help with an arm64 specific gcc internal error with polymake
On Sat, Nov 14, 2020 at 03:08:14PM +0000, Wookey wrote:
> On 2020-11-14 14:30 +0000, Dominic Hargreaves wrote:
> > On Wed, Nov 11, 2020 at 10:12:19PM +0000, Dominic Hargreaves wrote:
> > > During the perl 5.32 transition we observed a build failure on arm64 which
> > > is reproducible on the porterbox and at lease three different buidds::
> > >
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974073
>
> > Matthias theorized that this could be the OOM killer, which is why
> > it doesn't happen when built sequentially.
> >
> > Does anyone have access to a higher RAM machine than the buildds
> > and amdahl (11GiB) that could help test this theory (and maybe do a
> > porter upload to unblock the issue for the perl transition?
>
> Yes. I have a 64Gb machine. (emag).
>
> I have just tried it, and the file built OK, getting to a resident
> footprint of about 3.5G before completing.
>
> I'll try a polymake build/upload, and report back on the bug(s)
Thanks! I realised the new source-only policy for bullseye means this
probably wouldn't unblock the migration (unless the release team made
an exception) but it at least would give us an idea of how to move
forward.
Cheers
Dominic.
Reply to: