From: Randy MacLeod <randy.macleod@windriver.com>
To: Kang Kai <Kai.Kang@windriver.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: Could qt4.8 build on mips 64 bits platform?
Date: Thu, 27 Jun 2013 12:35:38 -0400 [thread overview]
Message-ID: <51CC69DA.3010406@windriver.com> (raw)
In-Reply-To: <51CC47DA.8090905@windriver.com>
On 13-06-27 10:10 AM, Kang Kai wrote:
> On 2013年06月25日 18:41, Paul Eggleton wrote:
>> On Tuesday 25 June 2013 17:32:48 Kang Kai wrote:
>>> Could qt4.8 build on mips 64 bits platform?
>>>
>>> I searched qt-project.org and no such related information.
>>> And then grep the source codethat no such mips64 keyword in file
>>> qmake.conf under directory mkspecs. In contrast there are mips32 related
>>> flags in mkspecs/qws/linux-mips-g++/qmake.conf.
>>>
>>> Does that mean we still can't build qt 4.8 on mips64?
>> I don't have any specific knowledge here; I'd suggest trying it. If
>> additional
>> patches are needed the best thing would be to try and get those merged
>> upstream.
>
> Thanks a lot. I'll try to build it on mips 64.
The background here is that we encountered many painful build problems
with qt-4.7 on mips64 in oe-core-1.2. We tried to fix them initially
but investigations from 6 months ago indicated that the qt upstream
did not support mips64. Kai will dig into the current situation
but I expect that little will have changed.
We ended up with horrid bbapends such as:
---
#Valid for all arches except mips64 with 64bit userspace
# mips64 with n32 has host: mips64-wrs-linux-gnun32
# mips64 with n64 has host: mips64-wrsmllib64-linux
# qemumips has host: mips-wrs-linux
# qemumips-64 has host: mips64-wrs-linux
COMPATIBLE_HOST =
'((x86_64.*|i.86.*|powerpc.*|arm.*|mips-.*|mips32.*)-linux|mips64.*-linux-gnun32)'
---
so we'll likely need a clue on how to declare a host as incompatible
or introduce an INCOMPATIBLE_HOST variable.
// Randy
>
> Regards,
> Kai
>
>>
>> Cheers,
>> Paul
>>
>
>
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350
next prev parent reply other threads:[~2013-06-27 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 9:32 Could qt4.8 build on mips 64 bits platform? Kang Kai
2013-06-25 10:41 ` Paul Eggleton
2013-06-27 14:10 ` Kang Kai
2013-06-27 16:35 ` Randy MacLeod [this message]
2013-06-27 16:46 ` Richard Purdie
2013-06-28 2:52 ` Kang Kai
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=51CC69DA.3010406@windriver.com \
--to=randy.macleod@windriver.com \
--cc=Kai.Kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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