Le lundi 30 septembre 2019 à 20:45 +0200, Paul Gevers a écrit : > On 30-09-2019 13:43, Emilio Pozuelo Monfort wrote: > > On 30/09/2019 11:56, Sébastien Villemot wrote:
> > > The new version (5.1.0-2) is now uploaded and built on all release > > > architectures, except on mipsel. The build failure seems transient to > > > me (memory exhausted), because version 5.1.0-1 built previously on the > > > same buildd, and there is nothing in the diff between the two versions > > > that can explain the problem. > > > > I have given it back. > > I tried it a second time. If it's three in a row, please check carefully > again. It failed to build for a 3rd time. So the problem is not transient, and I could reproduce it on the porterbox. For a given C++ source file, the generated assembly file is 303Mb large. Then the assembler hits the virtual space memory limit (which is only 2Gb on mipsel, if I understand correctly). The problem did not happen with the toolchain that was used to compile octave 5.1.0-1 (gcc 8 and binutils 2.31). However, I’m under the impression that it’s not really a bug, but rather another manifestation of the limitations of 32-bit architectures (as was discussed on -devel@ last August). I found two possible workarounds: either dropping -g, or replacing -O2 with -O. I’m tempted to drop -g for that particular file and particular arch. Does that seem ok to you? -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
signature.asc
Description: This is a digitally signed message part
