From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10541] New: QT5 package leaves out aarch64 in BR2_PACKAGE_QT5_JSCORE_AVAILABLE
Date: Mon, 04 Dec 2017 22:49:39 +0000 [thread overview]
Message-ID: <bug-10541-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10541
Bug ID: 10541
Summary: QT5 package leaves out aarch64 in
BR2_PACKAGE_QT5_JSCORE_AVAILABLE
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Outdated package
Assignee: unassigned at buildroot.uclibc.org
Reporter: jd.conley at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
I have been successfully building a QT5 application for aarch64 using the
Linaro toolchain, including QT5Declarative, which uses JSCore.
But I had to modify the qt5 package Config.in file.
Is this just an oversight or am I missing something and JSCore has some major
issues on aarch64? Looking at your git repo, architecture support for JSCore
appears to have not been updated for four years.
--- a/package/qt5/Config.in
+++ b/package/qt5/Config.in
@@ -7,7 +7,7 @@ config BR2_PACKAGE_QT5_JSCORE_AVAILABLE
bool
default y
# Javascript engine is only available on certain architectures
- depends on BR2_arm || BR2_i386 || BR2_x86_64 || BR2_mipsel
+ depends on BR2_arm || BR2_i386 || BR2_x86_64 || BR2_mipsel ||
BR2_aarch64
# ARM needs BLX, so v5t+
depends on !BR2_ARM_CPU_ARMV4
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-12-04 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 22:49 bugzilla at busybox.net [this message]
2017-12-05 17:23 ` [Buildroot] [Bug 10541] QT5 package leaves out aarch64 in BR2_PACKAGE_QT5_JSCORE_AVAILABLE bugzilla at busybox.net
2018-01-10 20:41 ` bugzilla at busybox.net
2018-01-15 22:20 ` bugzilla at busybox.net
2018-01-16 1:52 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-10541-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.