All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] firefox_3.6.8.bb: Mark as	COMPATIBLE_HOST="(powerpc|arm|i.86.*)".
Date: Tue, 21 Sep 2010 18:46:11 -0700	[thread overview]
Message-ID: <4C995FE3.3060601@mentor.com> (raw)
In-Reply-To: <4C995145.8090707@gmail.com>

Graham Gower wrote:
> Signed-off-by: Graham Gower <graham.gower@gmail.com>
> ---
>  recipes/mozilla/firefox_3.6.8.bb |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/recipes/mozilla/firefox_3.6.8.bb b/recipes/mozilla/firefox_3.6.8.bb
> index 825e692..b383de0 100644
> --- a/recipes/mozilla/firefox_3.6.8.bb
> +++ b/recipes/mozilla/firefox_3.6.8.bb
> @@ -1,6 +1,7 @@
>  DEPENDS += "cairo sqlite3 libnotify"
>  PR = "r1"
>  
> +COMPATIBLE_HOST = "(powerpc|arm|i.86).*"
>  # The .pc files below have "3.6" hardcoded, fix that before using them in a newer FF version!
>  SRC_URI = "ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/${PV}/source/firefox-${PV}.source.tar.bz2;name=archive \
>  	file://jsautocfg.h \


To sum up what I said on IRC, I'd really rather just go ahead and fix 
mipsel (and mips and ...) by pulling in the jsautocfg.h file from Debian 
or similar rather than use the more heavy handed COMPATIBLE* stuff for 
things that build in limited places by accident rather than by design. 
I don't know if that's enough for a NAK or not, but I'd like to talk it 
over a bit more :)

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-09-22  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22  0:43 [PATCH] firefox_3.6.8.bb: Mark as COMPATIBLE_HOST="(powerpc|arm|i.86.*)" Graham Gower
2010-09-22  1:46 ` Tom Rini [this message]
2010-09-22  6:14   ` Graham Gower

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=4C995FE3.3060601@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@lists.openembedded.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 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.