Your message dated Sun, 10 Jun 2018 17:03:38 -0400
with message-id
<CANTw=mors7v663njgzzgszz8z4h9cnjqdap0xlshjrrxm9d...@mail.gmail.com>
and subject line Re: Bug#897242: chromium: FTBFS on armhf: linker runs out of
memory
has caused the Debian Bug report #897242,
regarding chromium: FTBFS on armhf: linker runs out of memory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
897242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chromium-browser
Version: 66.0.3359.139-1
Severity: serious
Hi,
As you know, chromium has been failing to build on armhf for a while now.
That's specially bad as it's blocking testing migration, causing testing
users to run a pretty old version with several security vulnerabilities.
I see that you've tried to make it build there again (without much success).
I would suggest to try with -Wl,--no-keep-memory (which may not be very
effective with ld.gold though), -Wl,-O1 or -Wl,-O0 (rather than the current
-Wl,-O2).
You tried to disable debug symbols, but since the build logs are silent I
don't know if the code is still compiling with -g.
Thanks for looking at this,
Emilio
--- End Message ---
--- Begin Message ---
version: 67.0.3396.62-2
--- End Message ---
