Openembedded Core Discussions
 help / color / mirror / Atom feed
From: jhuang0 <jackie.huang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] midori: exclude from self-hosted for mips64
Date: Sat, 26 Oct 2013 09:40:05 +0800	[thread overview]
Message-ID: <526B1D75.40304@windriver.com> (raw)
In-Reply-To: <CAMKF1sqwHn4SU1U9_Cp0hsd8EKGYuteazX+OP7T5mQNDztPSsg@mail.gmail.com>



On 10/25/2013 8:32 PM, Khem Raj wrote:
> On Mon, Oct 21, 2013 at 11:04 PM,  <jackie.huang@windriver.com> wrote:
>> midori depends on webkit-gtk which could not build for mips64.
>
> what issues do you see building webkit-gtk for mips64, IIRC I fixed it
> some time ago

I didn't see the webkit-gtk issue, but I saw:
commit 0d2ed6bca55319195b5efd74eac83a459bf58ee8
Author: Kang Kai <kai.kang@windriver.com>
Date:   Fri Jul 5 10:18:10 2013 +0000

     webkit: set COMPATIBLE_HOST for mips64

     webkit packages can NOT be built for mips64 with 64 bit userspace. Set
     COMPATIBLE_HOST to to block them build for such platform.

     Signed-off-by: Kai Kang <kai.kang@windriver.com>
     Signed-off-by: Saul Wold <sgw@linux.intel.com>


and midori depends ot webkit-gtk so it's not buildable for mips64.
If it's fixed, I think you should reset the COMPATIBLE_HOST back for 
both webkitgtk and midori, thanks!

Thanks,
Jackie


>

-- 
Jackie Huang
WIND RIVER | China Development Center
MSN:jackielily@hotmail.com
Tel: +86 8477 8594
Mobile: +86 138 1027 4745


  reply	other threads:[~2013-10-26  1:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22  6:04 [PATCH 0/1] midori: exclude from self-hosted for mips64 jackie.huang
2013-10-22  6:04 ` [PATCH 1/1] " jackie.huang
2013-10-25 12:32   ` Khem Raj
2013-10-26  1:40     ` jhuang0 [this message]
2013-10-26  4:30       ` [PATCH 0/1] " Khem Raj

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=526B1D75.40304@windriver.com \
    --to=jackie.huang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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