All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Update qt to 4.7.3
Date: Fri, 13 May 2011 08:56:23 -0700	[thread overview]
Message-ID: <4DCD54A7.3080407@mentor.com> (raw)
In-Reply-To: <201105131144.27612.paul.eggleton@linux.intel.com>

On 05/13/2011 03:44 AM, Paul Eggleton wrote:
> On Thursday 12 May 2011 16:08:19 Tom Rini wrote:
>> Any idea if this fixes all of the arches that moving to 4.7.2 broke
>> (anything not arm or x86, more or less) ?  Thanks.
> 
> Which arches specifically didn't build for you? I have at least managed to 
> build 4.7.3 for x86-64 and MIPS (with oe-core that is).

In openembedded.master, mips*, ppc and sh4 don't compile past 4.7.1 but
I don't have the exact error handy (I think it was some dependency
library didn't support the arch).

-- 
Tom Rini
Mentor Graphics Corporation



      reply	other threads:[~2011-05-13 15:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 20:29 Update qt to 4.7.3 Eric Bénard
2011-05-11 20:30 ` [PATCH 1/6] qt4: introduce version 4.7.3 Eric Bénard
2011-05-12  8:47   ` Martin Jansa
2011-05-11 20:30 ` [PATCH 2/6] minimal: prefer qt 4.7.3 Eric Bénard
2011-05-12  8:32   ` Paul Menzel
2011-05-12  8:47     ` Michael 'Mickey' Lauer
2011-05-11 20:30 ` [PATCH 3/6] angstrom-2010: " Eric Bénard
2011-05-11 22:04   ` Koen Kooi
2011-05-11 20:30 ` [PATCH 4/6] kaeilos-2009: " Eric Bénard
2011-05-12  8:23   ` Marco Cavallini
2011-05-11 20:30 ` [PATCH 5/6] shr: " Eric Bénard
2011-05-12  8:47   ` Martin Jansa
2011-05-11 20:30 ` [PATCH 6/6] qt4: remove 4.7.2 Eric Bénard
2011-05-12  8:48   ` Martin Jansa
2011-05-12  1:21 ` Update qt to 4.7.3 Otavio Salvador
2011-05-12  7:40   ` Eric Bénard
2011-05-12  8:56 ` Paul Menzel
2011-05-12  9:11   ` Eric Bénard
2011-05-12 15:08 ` Tom Rini
2011-05-13 10:44   ` Paul Eggleton
2011-05-13 15:56     ` Tom Rini [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=4DCD54A7.3080407@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@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 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.