i386 build issue: "virtual memory exhausted: Operation not permitted"
Bug #1695903 reported by
Cesare Falco
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| launchpad-buildd |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I'm trying to build Mame new upstream release (0.186) and I'm getting the error
virtual memory exhausted: Operation not permitted
Please find the buildlog in attachment and on my PPA here:
https:/
The issue is limited to i386 arch.
Revision history for this message
| Cesare Falco (c.falco) wrote | #1 |
Revision history for this message
| Colin Watson (cjwatson) wrote | #2 |
| affects: | launchpad → launchpad-buildd |
| Changed in launchpad-buildd: | |
| status: | New → Invalid |
To post a comment you must log in.
This isn't really an issue with Launchpad or its builders as such. A 32-bit x86 process running on a 64-bit kernel (the configuration we use for i386 builds) can only address up to 4GiB of memory in a single process, regardless of how much RAM and swap is available to it. In this case it looks as though a particular C++ file is especially fat and causes g++ to try to allocate more than that amount of memory. There's nothing we can do about that from the Launchpad side of things.
You will have to investigate compiler flags that might cause it to use less memory (e.g. decreasing optimisation for that file) or working with upstream to split it up into smaller compilation units.