[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



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 garbage collector's heap should be allowed to expand between collections. Tuning this may improve compilation speed; it has no effect on code generation.

The file qrc_resources.cxx is quite large (66M), is it possible to split it?


Regards,
Dejan

________________________________________
From: Yaroslav Halchenko [yoh@dartmouth.edu]
Sent: Wednesday, October 12, 2016 2:28 AM
To: debian-mips@lists.debian.org
Cc: Timothy Coalson
Subject: how to deal with "virtual memory exhausted: Cannot allocate memory"?

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... ? ;)

Please CC us in reply
--
Yaroslav O. Halchenko
Center for Open Neuroscience     http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


Reply to: