All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Release-2011.03 status
Date: Mon, 28 Feb 2011 08:31:42 -0700	[thread overview]
Message-ID: <4D6BBFDE.2090406@mentor.com> (raw)

Hey all,

Over at http://dl.dropbox.com/u/3284539/ac9745f0fe_results.pdf you can 
see the results of my build over the weekend.  It's a bit scary but...

Fixed:
- minimal-uclibc/*/* was broken due to needing xattr in DISTRO_FEATURES
- ucslug/sheevaplug/* was broken due to TARGET_ARCH in distro.conf

Not fixed:
antgw100: Needs the linux/socket.h > sys/socket.h thing someone else 
mentioned.
various/angstrom*/angstrom-gnome-image: evince needs various docbook 
things installed that we don't build, don't force the host to have and 
isn't 100% trivial to switch to building (I've started on this path but 
haven't gotten it quite right).
- various/shr/shr-image: The libvpx work-around 
(http://patches.openembedded.org/patch/256/) to link.
- qemux86/minimal*/*: A hard RPATH issue where we're getting away, 
usually, with libXrandr from the host, but this build host is really 
stripped down.  I bisected this down to when we fixed RPATH stuff in 
9432df5a1c96f7b2e625abba0e011ad45d5aef92 and it's a bug in some recipe.
- various/shr/shr-image: A problem with python-elementary/elementary 
disagreeing on version stuff, will post later.

So, my current plan of attack is to do what I've said before and merge 
the libvpx work-around, tag, revert the libvpx work-around (per Khem's 
request).  And I plan to do this tomorrow unless people shout about 
wanting to fix something they know is broken and need a little more time.

-- 
Tom Rini
Mentor Graphics Corporation



             reply	other threads:[~2011-02-28 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 15:31 Tom Rini [this message]
2011-02-28 17:01 ` Release-2011.03 status Stefan Schmidt
2011-02-28 18:48   ` Tom Rini
2011-03-01 18:16     ` Stefan Schmidt

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=4D6BBFDE.2090406@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.