Bug#1002568: ogre-1.12: FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory

[Simon McVittie]

Control: severity -1 important
Control: retitle -1 ogre-1.12: FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory
Control: found -1 1.12.10+dfsg2-2~exp3

On Fri, 24 Dec 2021 at 11:40:57 +0100, Bastian Germann wrote:
> ogre-1.12 does not build on sid/mipsel:
> https://buildd.debian.org/status/fetch.php?pkg=ogre-1.12&arch=mipsel&ver=1.12.10%2Bdfsg2-1.2&stamp=1640306818&raw=0

ogre-1.12 has never built successfully on mipsel, so I don't think this is
RC unless a maintainer or the Release Team says it is. FTBFS on a single
architecture is generally only RC if it's a regression, and not if that
architecture has never been built successfully.

This looks like the root cause, which wil not be easy to fix:

> virtual memory exhausted: Cannot allocate memory

It might be possible to apply some tricks to make the build take less
memory. I see Olek Wojnar has made a couple of attempts at this in
experimental, but unfortunately without success so far.

webkit2gtk is an example of another package that hits memory
limits during build. It currently uses LDFLAGS += -Wl,--no-keep-memory
on 32-bit architectures (a time/space trade-off), and $(CFLAGS:-g=-g1)
to reduce the size and coverage of its detached debug symbols.

    smcv