Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 0/5] toolchain bootstrap fixes and kernel.bbclass integration
Date: Thu, 26 Jul 2012 12:15:28 -0700	[thread overview]
Message-ID: <50119750.7080109@linux.intel.com> (raw)
In-Reply-To: <cover.1343142062.git.raj.khem@gmail.com>

On 07/24/2012 08:03 AM, Khem Raj wrote:
> This patchset fixes isssue with compiling toolchain's bootstrap elements
> added changes from kernel.bbclass from meta-oe
> Fixes eglibc when certain options are disabled (seen on poky-tiny)
>
> The following changes since commit 4148bc80c008d25c8a536c7c7dfdeac1669a6662:
>
>    libgcc: Add missing dependency on libc:do_package (2012-07-24 10:12:08 +0100)
>
> are available in the git repository at:
>
>    git://git.openembedded.org/openembedded-core-contrib kraj/misc-updates
>    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=master
>
> Denis Carikli (1):
>    kernel.bbclass: fix external module building
>
I held back this one as I think there is still some discussion on it.

> Khem Raj (3):
>    eglibc-initial: Fix build failure due to missing limits.h
>    gcc-cross-initial: Stage self sufficient fixed limits.h
>    eglibc: Fix build when OPTION_POSIX_WIDE_CHAR_DEVICE_IO is not set
>
> Koen Kooi (1):
>    kernel bbclass: Recreate uImage only when KEEPUIMAGE != "yes"
>
Merged the above 4 patches into OE-Core

Thanks	
	Sau!
>   meta/classes/kernel.bbclass                        |    5 +-
>   meta/conf/distro/include/default-distrovars.inc    |    1 +
>   .../eglibc/eglibc-2.16/GLRO_dl_debug_mask.patch    |   48 ++++++++++++++------
>   .../eglibc-2.16/fileops-without-wchar-io.patch     |   22 +++++++++
>   meta/recipes-core/eglibc/eglibc-initial.inc        |    1 +
>   meta/recipes-core/eglibc/eglibc-initial_2.16.bb    |    9 ++--
>   meta/recipes-core/eglibc/eglibc_2.16.bb            |    3 +-
>   meta/recipes-devtools/gcc/gcc-4.7.inc              |    2 +-
>   meta/recipes-devtools/gcc/gcc-cross-initial.inc    |   10 ++++
>   9 files changed, 82 insertions(+), 19 deletions(-)
>   create mode 100644 meta/recipes-core/eglibc/eglibc-2.16/fileops-without-wchar-io.patch
>




  parent reply	other threads:[~2012-07-26 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 15:03 [PATCH 0/5] toolchain bootstrap fixes and kernel.bbclass integration Khem Raj
2012-07-24 15:04 ` [PATCH 1/5] kernel.bbclass: fix external module building Khem Raj
2012-07-24 15:04 ` [PATCH 2/5] kernel bbclass: Recreate uImage only when KEEPUIMAGE != "yes" Khem Raj
2012-07-24 15:04 ` [PATCH 3/5] eglibc-initial: Fix build failure due to missing limits.h Khem Raj
2012-07-24 15:04 ` [PATCH 4/5] gcc-cross-initial: Stage self sufficient fixed limits.h Khem Raj
2012-07-24 16:54   ` Otavio Salvador
2012-07-24 15:04 ` [PATCH 5/5] eglibc: Fix build when OPTION_POSIX_WIDE_CHAR_DEVICE_IO is not set Khem Raj
2012-07-26 19:15 ` Saul Wold [this message]
2012-07-26 20:15   ` [PATCH 0/5] toolchain bootstrap fixes and kernel.bbclass integration 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=50119750.7080109@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox