Closed Bug 1503747 Opened Last year Closed Last year
Skia m71 (Firefox 65 branch) fails to build on big endian systems
The new Skia code that landed in bug 1502152 breaks building on big-endian again (somewhat a regression of 849253 or 1144632 if you want to go so far). Patches from Marcus Comstedt that are being upstreamed to Chromium (see https://wiki.raptorcs.com/wiki/Porting/Chromium/BE etc) fix the build on BE targets.
Squashed HG commit of the two Chromium git patches.
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/20ae9023dd79 don't build unused SkJSON. r=me
Comment on attachment 9021712 [details] [diff] [review] Fix Skia build on big-endian targets These patches are unnecessary as we can just disable building of SkJSON entirely, it turns out.
Assignee: nobody → lsalzman
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
That fixes the SkJSON issue, but not the SkCodecPriv.h file missing the SkEndian.h inclusion. I'll make a new patch that contains just that fix.
This is not resolved. I specifically mentioned that the SkCodecPriv.h file still needs to be fixed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This drops the SkJSON patches that are unnecessary since SkJSON is NPOTB now.
(In reply to A. Wilcox [:awilfox] from comment #7) > Created attachment 9022015 [details] [diff] [review] > Fix Skia build on big-endian targets > > This drops the SkJSON patches that are unnecessary since SkJSON is NPOTB now. Why is the SkEndian.h header necessary to include there? We don't build any of the actual codecs, so I am not sure how this would affect anything.
Comment on attachment 9022015 [details] [diff] [review] Fix Skia build on big-endian targets Oh, I see. SkCodecPriv.h uses some EndianSwaps conditionally on big-endian.
Attachment #9022015 - Flags: review?(lsalzman) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/61f04931011f Fix Skia build on big-endian targets. r=lsalzman
Status: REOPENED → RESOLVED
Closed: Last year → Last year
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.