Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

2019-05-03 Thread Drew Parsons
On 2019-05-03 16:54, Nico Schlömer wrote: cf. https://stackoverflow.com/questions/55801777/set-compile-flags-when-installing-python-c-project Disturbingly bad help these people are giving us :( Do they ever try the "solutions" they're providing? Even the sysconfig version, all it does is

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

2019-05-03 Thread Nico Schlömer
cf. https://stackoverflow.com/questions/55801777/set-compile-flags-when-installing-python-c-project On Fri, May 3, 2019 at 10:29 AM Drew Parsons wrote: > > On 2019-05-03 16:24, Nico Schlömer wrote: > >> Do you know how to control it? > > > > I'd been looking at this once, to no avail. Locally

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

2019-05-03 Thread Drew Parsons
On 2019-05-03 16:24, Nico Schlömer wrote: Do you know how to control it? I'd been looking at this once, to no avail. Locally I just use CC=clang++ now. It's very odd that they make it difficult to deal with. The offending definition looks like OPT in

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

2019-05-03 Thread Nico Schlömer
> Do you know how to control it? I'd been looking at this once, to no avail. Locally I just use CC=clang++ now. On Fri, May 3, 2019 at 10:11 AM Drew Parsons wrote: > > On 2019-04-29 15:49, Nico Schlömer wrote: > >> No easy way around it. > > > > Indeed. > > > >> Building with -g -O1 (or -O2

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

2019-05-03 Thread Drew Parsons
On 2019-04-29 15:49, Nico Schlömer wrote: No easy way around it. Indeed. Building with -g -O1 (or -O2 without -g) helps mshr, we can test if it helps pygalmesh too. Removing `-g` almost certainly improves things. Using clang++ instead of c++ also helps. I can remove Debian's -g flag

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

2019-04-29 Thread Nico Schlömer
> No easy way around it. Indeed. > Building with -g -O1 (or -O2 without -g) helps mshr, we can test if it helps > pygalmesh too. Removing `-g` almost certainly improves things. Using clang++ instead of c++ also helps. On Mon, Apr 29, 2019 at 9:06 AM Drew Parsons wrote: > > Source: pygalmesh

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

2019-04-29 Thread Drew Parsons
Source: pygalmesh Followup-For: Bug #928140 Not a regression as such: 0.2.6-1 also exhausts memory on i386 sometimes (not always), cf. https://tests.reproducible-builds.org/debian/logs/unstable/i386/pygalmesh_0.2.6-1.build2.log.gz This is a general problem with meshing libraries. mshr has a

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

2019-04-28 Thread Andreas Beckmann
Source: pygalmesh Version: 0.3.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, pygalmesh/experimental FTBFS on the 32-bit architectures i386, armhf because it runs out of (virtual) memory. This is a regression compared to sid.