Note: adding debian-arm to cc for feedback from other porters. Jonathan Nieder wrote:
Like any other package if chromium gives us problems over in raspbian I will try to get those problems fixed and will contribute what I discover back to debian where appropriate but I don't have any real knowlege of chromium's internals or build system nor do I have the time or inclination to learn them.Hi Peter, peter green wrote:Patch to make the package use bfd rather than gold on armel and armhf is attached. I may or may not upload this as a NMU.If you'll have time to continue working on chromium:arm in the future, it would probably be better to just add yourself to pkg-chromium on alioth
Anyway I have some bad news. When I try to do an armel build with bfd on my imx board I get.
LINK(target) out/Release/chrome /usr/bin/ld.bfd.real: failed to set dynamic section sizes: Memory exhausted collect2: ld returned 1 exit statusI have plenty of swap so i'm pretty sure the real problem is not memory per-se but address space. I had the same problem with the raspbian build (but not with the debian armhf build) and for raspbian I worked arround it by building with user mode qemu on an x64 host (which provides significantly more virtual address space than any real arm system) but i'm not sure that is acceptable for debian.
Thoughts on what to do for chromium on armel? leave it broken? drop it completely? upload packages built with bfd under user mode qemu (assuming that succeeds and produces usable packages) to the archive?