From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-09
Date: Tue, 11 Nov 2014 12:10:50 +0000 [thread overview]
Message-ID: <5461FCCA.1000306@imgtec.com> (raw)
In-Reply-To: <20141110191617.43273fde@free-electrons.com>
Dear Thomas Petazzoni,
On 11/10/2014 06:16 PM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
>
> On Mon, 10 Nov 2014 15:58:48 +0000, Vicente Olivert Riera wrote:
>> On 11/10/2014 03:53 PM, Vicente Olivert Riera wrote:
>>> On 11/10/2014 07:30 AM, Thomas Petazzoni wrote:
>>>> mips64el | qt-4.8.6 | NOK | http://autobuild.buildroot.net/results/bb8ab5ea7ed02cf17c46522903b4e46035e47f16/
>>>
>>> I thought this was already fixed upstream... I need to report this
>>> again. It's a failure with MIPS64 n32, probably because it's not taken
>>> into account that MIPS64 n32 has 32-bit pointers and integers instead of
>>> 64-bit.
>>
>> Ok, sorry. qt-4.8.6 was fixed upstream (I did it). The problem here is
>> with qt-webkit, which I already reported upstream:
>>
>> https://bugreports.qt-project.org/browse/QTBUG-39224
>
> May disallow on MIPS64 n32 for the moment?
hehehe... :D
Do you remember when we talked about finding which architectures support
BR2_PACKAGE_QT_SCRIPT to create a new
BR2_PACKAGE_QT_ARCH_SUPPORTS_SCRIPT in order to differentiate them from
BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT? Because BR2_PACKAGE_QT_SCRIPT
builds fine for MIPS64 n32, but it depends on
BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT. So, if you disable
BR2_PACKAGE_QT_ARCH_SUPPORTS_WEBKIT for MIPS64 n32 then you will be
disabling BR2_PACKAGE_QT_SCRIPT as well. That's why few months ago I
wanted to disable only BR2_PACKAGE_QT_WEBKIT for MIPS64 n32, but then
you told me "Hey, there is something wrong here! We need to know which
architectures support qt-script and which ones support qt-webkit".
Best regards,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
next prev parent reply other threads:[~2014-11-11 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-09 Thomas Petazzoni
2014-11-10 7:48 ` Baruch Siach
2014-11-10 15:53 ` Vicente Olivert Riera
2014-11-10 15:58 ` Vicente Olivert Riera
2014-11-10 18:16 ` Thomas Petazzoni
2014-11-11 12:10 ` Vicente Olivert Riera [this message]
2014-11-11 13:03 ` Thomas Petazzoni
2014-11-11 13:34 ` 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=5461FCCA.1000306@imgtec.com \
--to=vincent.riera@imgtec.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 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.