Hello everybody, what's the status of this bug? I would love to see chromium on armhf and arm64.
Michael, it looks like Riku upstreamed most of the important changes and what's left is reasonable to include in the Debian package. Cheers, On Thu, 26 Nov 2015, Riku Voipio wrote: > Hi, > > Michael wrote: > > > These changes are larger than I would like. Please upstream them > > first, especially the assembly changes to openmax. > > Submitted and applied upstream: https://codereview.chromium.org/1420973006/ > Sandbox patch is also applied, and boringssl compiler flag changes has just > been > submitted. > > On 18 November 2015 at 23:26, Joost van Zwieten > <[email protected]> wrote: > > On 3 November 2015 at 20:37, Joost van Zwieten > > <[email protected]> wrote: > > That took a bit longer than expected. With the latest binutils from > > experimental I was still unable to link chromium: ld failed with the > > message 'Memory exhausted'. I came up the following solution: reduce > > the amount of debug information to line numbers only. Passing > > '-gline-tables-only' to clang does the job, see fourth attached patch. > > With all patches applied I can successfully build chromium. > > I've verified that linking succeeds with these change on abel.debian.org, > which is identical to the Debian armhf builders. > > Attached is the combined patch of my arm64 changes and Joost's armhf changes > against the experimental version of chromium: > > ps. notice the vaapi.patch is broken. It assumes the tests "arch!=arm" and > "arch = x86" are identical. -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
