Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Split supported architectures for Qt Script and Qt Webkit
Date: Fri, 28 Nov 2014 00:57:55 +0100	[thread overview]
Message-ID: <87tx1kmc1o.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <546DD5C9.8090600@imgtec.com> (Vicente Olivert Riera's message of "Thu, 20 Nov 2014 11:51:37 +0000")

>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:

 > Dear all,
 > please I would like you read this email and provide some feedback before
 > I start writing a patch.

Thanks for investigating!

 > I have assigned a code to each kind of problem I have found, and the
 > meaning of those codes are just below the table.

 > +------------------+-----------+-----------+----------+--------------+
 > | Architecture     | Qt Script | Qt Webkit | Grantlee | Problem Code |
 > +------------------+-----------+-----------+----------+--------------+
 > | BR2_aarch64      | YES       | NO        | YES      | 2            |
 > | BR2_nios2        | YES       | NO        | NO       | 4            |

So the only ones not covered today are these two, right? What about the
mips variant you mentioned above?

The BR2_aarch64 issue will presumably be solved in future qtwebkit
releases once the arch gets a bit more used. The nios issue is an
internal compiler error, that is less likely to get fixed (until a new
compiler is released atleast).

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2014-11-27 23:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 11:51 [Buildroot] Split supported architectures for Qt Script and Qt Webkit Vicente Olivert Riera
2014-11-24 10:44 ` Vicente Olivert Riera
2014-11-27 23:57 ` Peter Korsgaard [this message]
2014-11-28 10:05   ` Vicente Olivert Riera

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=87tx1kmc1o.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox