Patchwork [0/5] toolchain bootstrap fixes and kernel.bbclass integration

login
register
mail settings
Submitter Khem Raj
Date July 24, 2012, 3:03 p.m.
Message ID <cover.1343142062.git.raj.khem@gmail.com>
Download mbox
Permalink /patch/32941/
State New
Headers show

Pull-request

git://git.openembedded.org/openembedded-core-contrib kraj/misc-updates

Comments

Khem Raj - July 24, 2012, 3:03 p.m.
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

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"

 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
Saul Wold - July 26, 2012, 7:15 p.m.
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
>
Khem Raj - July 26, 2012, 8:15 p.m.
On Thu, Jul 26, 2012 at 12:15 PM, Saul Wold <sgw@linux.intel.com> wrote:
>>
>> Denis Carikli (1):
>>    kernel.bbclass: fix external module building
>>
> I held back this one as I think there is still some discussion on it.

Discussion is not on review of this patch. Infact discussion was more
about the recently
added feature that casued this issue to start with.