Bug 1070446 - Add support for aarch64
Summary: Add support for aarch64
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: qtwebkit
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1046360
Blocks: ARM64, F-ExcludeArch-aarch64
TreeView+ depends on / blocked
 
Reported: 2014-02-26 20:58 UTC by Rex Dieter
Modified: 2014-03-24 12:16 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1046360
Environment:
Last Closed: 2014-03-24 12:16:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
add aarch64 support (940 bytes, patch)
2014-02-28 18:31 UTC, Rex Dieter
no flags Details | Diff
AArch64 patch + disable JIT (3.14 KB, patch)
2014-02-28 20:20 UTC, Marcin Juszkiewicz
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Qt Bug Tracker QTBUG-35442 0 None None None Never

Description Rex Dieter 2014-02-26 20:58:10 UTC
Need to port the javascriptcore/webkit bits to qtwebkit packaging...




+++ This bug was initially created as a clone of Bug #1046360 +++

It's been reported upstream (link below) but it would be useful to get aarch64 support into rawhide to enable easier building of qt and the many packages it's dependent on.

https://bugreports.qt-project.org/browse/QTBUG-35442

Build here http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=2193755

--- Additional comment from Rex Dieter on 2014-01-03 08:02:34 EST ---

imported, thanks.

%changelog
* Mon Dec 23 2013 Peter Robinson <pbrobinson> 4.8.5-13
- Add support for aarch64 (#1046360)

Comment 1 Peter Robinson 2014-02-26 22:51:58 UTC
I think this is mixing qt and qtwebkit? Or do you have the NVR for qtwebkit too?

Comment 2 Rex Dieter 2014-02-26 23:08:45 UTC
I saw the aarch64 qtwebkit build failures, and I think it's due, in part, to similar fixes made to the bundled copy of webkit in qt tarball.

Comment 3 Peter Robinson 2014-02-26 23:10:53 UTC
At the moment the issue is primarily missing or other dep issues which I'm working through, once I get them in place if it still fails I'll update this. Thanks!

Comment 4 Peter Robinson 2014-02-26 23:22:34 UTC
(In reply to Peter Robinson from comment #3)
> At the moment the issue is primarily missing or other dep issues which I'm
> working through, once I get them in place if it still fails I'll update
> this. Thanks!

Oh god ignore me, we're past that bit... it's been a long day.

Comment 5 Peter Robinson 2014-02-26 23:29:55 UTC
if you happen to have a patch :-)

Comment 6 Rex Dieter 2014-02-28 18:30:58 UTC
Have a proof-of-concept port, scatch build underway,

http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=2247749

Comment 7 Rex Dieter 2014-02-28 18:31:58 UTC
Created attachment 869151 [details]
add aarch64 support

Comment 8 Rex Dieter 2014-02-28 19:27:35 UTC
OK, pulled in the latest aarch64-related bits from upstream qt5 qtwebkit repo, and it's still failing on:

webkit-qtwebkit-23/Source/JavaScriptCore/assembler/MacroAssembler.h:62:2: error: #error "The MacroAssembler is not supported on this platform."

:( I'm a bit stumped now.  I'll commit what I have to rawhide.

Comment 9 Rex Dieter 2014-02-28 19:33:37 UTC
Marcin, can you give any advice here?

I tried a basic backport of the changes from qt5-qtwebkit and bug #1056160 to qt4's webkit here, but there's apparently more to it... seems related to javascript jit support.

Comment 10 Marcin Juszkiewicz 2014-02-28 20:20:22 UTC
Created attachment 869193 [details]
AArch64 patch + disable JIT

This patchset gets us a bit further. There is not JIT for AArch64 so we need to disable it.

Build failed anyway as there is 5.3GB of object files which "ar" is unable to convert into libWebCore.a - looks like 4GB limit.

Comment 11 Kevin Kofler 2014-02-28 22:54:49 UTC
Add aarch64 to this patch:
http://pkgs.fedoraproject.org/cgit/qtwebkit.git/tree/qtwebkit-2.3-debuginfo.patch
or make it unconditional altogether. (The conditionals are inside the patch.)


Note You need to log in before you can comment on or make changes to this bug.