Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?
Adrian Bunk <[email protected]>
| Newsgroups | gmane.linux.debian.ports.mips |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Oct 11, 2016 at 08:28:28PM -0400, Yaroslav Halchenko wrote: > Hi MIPS gurus, > > We have > Bug#837403: connectome-workbench: FTBFS with bindnow and PIE > due to inability to build that package on mips > https://buildd.debian.org/status/fetch.php?pkg=connectome-workbench&arch=mips&ver=1.2.3-2&stamp=1473733739 > or mipsel > https://buildd.debian.org/status/fetch.php?pkg=connectome-workbench&arch=mipsel&ver=1.2.3-2&stamp=1473733554 > > both of which fail with > > "virtual memory exhausted: Cannot allocate memory" > > What would be your recommendation -- demand removing mips* from > supported architectures or there is a chance... ? ;) The build log says make -j4 This is due to the following in debian/rules: dh $@ --parallel --sourcedirectory=src Running 4 instances of the compiler in parallel can quadruple the memory usage. Does the build succeed when you make that non-parallel on mips? > Please CC us in reply cu Adrian