Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
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: Fri, 28 Jun 2013 10:52:39 +0800	[thread overview]
Message-ID: <51CCFA77.4080506@windriver.com> (raw)
In-Reply-To: <1372351613.9930.225.camel@ted>

On 2013年06月28日 00:46, Richard Purdie wrote:
> On Thu, 2013-06-27 at 12:35 -0400, Randy MacLeod wrote:
>> 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.
> I suspect something like this should work:
>
> COMPATIBLE_HOST_mips64 = ""

Thanks.

We still need include such packages on mips64 with 32 bits filesystem.  
So the following is needed:

COMPATIBLE_HOST_mips64 = "mips64.*-linux-gnun32"

I am little worried that "-gnun32" is a standard name then I'll figure it out.

Regards,
Kai


>
> Cheers,
>
> Richard
>
>


-- 
Regards,
Neil | Kai Kang



      reply	other threads:[~2013-06-28  2:53 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
2013-06-27 16:46       ` Richard Purdie
2013-06-28  2:52         ` Kang Kai [this message]

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=51CCFA77.4080506@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=richard.purdie@linuxfoundation.org \
    /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