Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-15 Thread Yaroslav Halchenko
On Sat, 15 Oct 2016, Adrian Bunk wrote: > > > 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. > > That is true,

Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-15 Thread Jeffrey Walton
>> Does anyone know what kind of board is being used? What are its cpu >> and memory specs? Does /proc/meminfo report a swap file? > > https://db.debian.org/machines.cgi?host=mipsel-manda-03 > Memory: 8GB Oh, thanks. I was not aware the machine had requisite horse power. Sorry about that. Jeff

Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-15 Thread Aurelien Jarno
On 2016-10-15 11:00, Yaroslav Halchenko wrote: > > On Sat, 15 Oct 2016, Adrian Bunk wrote: > > > > 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

Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-15 Thread James Cowgill
Hi, On 15/10/16 13:10, Jeffrey Walton wrote: "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

Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-15 Thread Adrian Bunk
On Sat, Oct 15, 2016 at 01:51:07PM +0200, Aurelien Jarno wrote: > On 2016-10-14 14:12, Adrian Bunk wrote: > > 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

Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-15 Thread Jeffrey Walton
>> > "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 $@

Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-15 Thread Aurelien Jarno
On 2016-10-14 14:12, Adrian Bunk wrote: > 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 > >

Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-14 Thread Yaroslav Halchenko
On Fri, 14 Oct 2016, Adrian Bunk wrote: > 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 > >

Re: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-14 Thread Adrian Bunk
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 >

RE: how to deal with "virtual memory exhausted: Cannot allocate memory"?

2016-10-14 Thread Dejan Latinovic
Hi, I have tried to solve this issue using ggc-min-expand flag, it helped in similar issues in the past, but in this case it did not worked. > ggc-min-expand > GCC uses a garbage collector to manage its own memory allocation. This > parameter specifies the minimum percentage by which the