<html><head/><body><html><head></head><body>It works when built with gold 2.23 on an armv6+ hardware host (bug 696284). This bug is also a dup, and was njotriced shortely after chromium 22 was made to build again on arm (ftbfs since chromium 18) due to my patches.<br><br><div class="gmail_quote">peter green <plugwash@p10link.net> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px">Note: adding debian-arm to cc for feedback from other porters.<br /><br />Jonathan Nieder wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Hi Peter,<br /><br />peter green wrote:<br /><br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">Patch to make the package use bfd rather than gold on armel and armhf is<br />attached. I may or may not upload this as a NMU.</blockquote><br /><br />If you'll have time to continue working on chromium:arm in the future,<br />it would probably be better to just add yourself to pkg-chromium on<br />alioth<br /></blockquote>Like any other package if chromium gives us problems over in raspbian I <br />will try to get those problems fixed and will contribute what I discover <br />back to debian where
appropriate but I don't have any real knowlege of <br />chromium's internals or build system nor do I have the time or <br />inclination to learn them.<br /><br />Anyway I have some bad news. When I try to do an armel build with bfd on <br />my imx board I get.<br />LINK(target) out/Release/chrome<br />/usr/bin/ld.bfd.real: failed to set dynamic section sizes: Memory exhausted<br />collect2: ld returned 1 exit status<br /><br />I have plenty of swap so i'm pretty sure the real problem is not memory <br />per-se but address space. I had the same problem with the raspbian build <br />(but not with the debian armhf build) and for raspbian I worked arround <br />it by building with user mode qemu on an x64 host (which provides <br />significantly more virtual address space than any real arm system) but <br />i'm not sure that is acceptable for debian.<br /><br />Thoughts on what to do for chromium on armel? leave it broken? drop it <br />completely? upload packages built with bfd under
user mode qemu <br />(assuming that succeeds and produces usable packages) to the archive?<br /><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html></body></html>