[Debichem-devel] Bug#738137: Bug#738137: libpwiz: FTBFS on mips*: virtual memory exhausted

[Michael Banck]

Hi,

On Mon, Feb 10, 2014 at 09:43:54PM +0100, Filippo Rusconi wrote:
> On Sat, Feb 08, 2014 at 01:13:37AM +0100, Andreas Beckmann wrote:
> >Source: libpwiz
> >Version: 3.0.4624-7
> >Severity: serious
> >
> >Hi,
> >
> >your package failed to build on mips and mipsel:
> >
> >https://buildd.debian.org/status/package.php?p=libpwiz
> >
> >with
> >
> >virtual memory exhausted: Cannot allocate memory
> >make[2]: *** [pwiz/data/identdata/IdentData.lo] Error 1
> >
> >
> >Maybe disabling parallel builds on mips* could help.
> 
> I am planning to put this in debian/rules on top of all the targets:
> 
> ifeq ("mips-linux-gnu",$(DEB_HOST_GNU_TYPE))
> .NOTPARALLEL: endif
> 
> Do you think that this might work? I mean, are the mips systems
> characterized by this string: "mips-linux-gnu"

I believe one can simulate the answer to this question via
dpkg-architecture and setting the Debian arch:

$ dpkg-architecture -amips -qDEB_HOST_GNU_TYPE
dpkg-architecture: warning: specified GNU system type mips-linux-gnu
 does not match gcc system type x86_64-linux-gnu, try setting a correct
 CC environment variable
mips-linux-gnu
$ dpkg-architecture -amipsel -qDEB_HOST_GNU_TYPE
dpkg-architecture: warning: specified GNU system type mipsel-linux-gnu
 does not match gcc system type x86_64-linux-gnu, try setting a correct
 CC environment variable
mipsel-linux-gnu
$ 

So it seems one has to special case both mips and mipsel.

Just to mention, the same issue (virtual memory exhausted: Cannot
allocate memory) came up in a discussion on #debian-devel the other day
and people were rather pessimistic that deactivating parallel builds
would help.  But I guess it is worth a shot.


Michael