Chromium build on TC 3.0.21

[n3ond4x]

Hey guys,

I'm trying to build my own custom 32-bit chromium build for TC and I'm struggling because it requires roughly 8-10 gbs of memory to link and the 32-bit TC instance I'm compiling on cannot support more than 3gb of memory. Does anyone have any good suggestions for how to handle this?

Thanks a lot.

[Rich]

Hi n3ond4x

it requires roughly 8-10 gbs of memory to link

That sounds excessive. Try putting the source package in a persistent directory and build from there.

[n3ond4x]

I sourced that from the chromium build wiki but I can't find it as of right now. However I know for a fact it is using more than the 3gb a 32bit kernel can handle. The source is being built on a persistent harddisk not in memory, the final linking stage is when all of the object code and dynamic libraries need to be loaded into actual memory.

[bmarkus]

Why don't you ask extension creator for details?

[Rich]

Hi n3ond4x
Read the  Memory space  paragraph here:
http://code.google.com/p/chromium/wiki/LinuxBuildInstructionsPrerequisites

[n3ond4x]

Thanks Rich, I read that before "It takes about 8GB of swap file to link chromium and its tests. If you get an out-of-memory error during the final link, you will need to add swap space with swapon." and I've got a 20gb swap partition enabled just for this.

Here is the error I'm receiving. "gold32 fatal error mmap: failed to allocate 1509484464 bytes for output file: cannot allocate memory."
That's around 1.4gb.

The maintainer of the package is Arslan S. I'll try and find him and send him a PM

[bmarkus]

Are you building static or shared, with or w/o test?

[n3ond4x]

 It's dynamic/shared. The only command I am passing is "make chrome". Which is what is suggested in the build instructions. All of the object code has successfully compiled, it's the linking that is failing.

[curaga]

I think they use 64-bit machines and cross-compile because Chromium's too big like that. But perhaps a shared release build fits in the normal 32-bit limits.

[Rich]

Hi n3ond4x
I found this:

Code: [Select]

LDFLAGS="-Wl,--reduce-memory-overheads"here:
http://old.nabble.com/Out-of-memory-on-OBS-issue-for-Chromium-td33384307.html
See here:
http://linux.die.net/man/1/ld
for what  --reduce-memory-overheads  does.

[bmarkus]

I think they use 64-bit machines and cross-compile because Chromium's too big like that. But perhaps a shared release build fits in the normal 32-bit limits.

When I checked a month ago I decided not try to build on Raspberry Pi 

[n3ond4x]

curaga: Any idea on how I could go about doing that? Could it be as simple as replacing my 32bit kernel with a 64bit kernel? I haven't found any instructions that don't claim to be obsolete on the chromium wiki.

rich: I keep getting "--reduce-memory-overheads: unknown option" when I add "-Wl,--reduce-memory-overheads" to my LDFLAGS

Thanks again guys.

[bmarkus]

It's dynamic/shared. The only command I am passing is "make chrome". Which is what is suggested in the build instructions. All of the object code has successfully compiled, it's the linking that is failing.

Disable building tests as written in WIKI.

[n3ond4x]

I'm not building any tests. "make chrome" makes chrome specifically (or chromium) in debug mode. Which includes a lot of debug symbols I realize, however I don't see why I should be limited by that. I would very much like it to just use whatever swap space I have available to finish the link. Is there any special PAE build of the 32bit kernel I could use or something similar?

[bmarkus]

BTW, what is wrong with the repo version?