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>
Subject: Re: [v2 0/4] grub & eglibc fixes for fedora 17 alpha
Date: Mon, 16 Apr 2012 08:36:45 -0700	[thread overview]
Message-ID: <4F8C3C8D.3050801@linux.intel.com> (raw)
In-Reply-To: <cover.1334390876.git.nitin.a.kamble@intel.com>

On 04/14/2012 01:59 AM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>
> These are various grub fixes for correctly building grub recipes for various targets.
> These are tested for emenlow, sugerbay, qemux86, qemux86-64 machines
>
> The eglibc commits is thes same as in the v1 pull request.
>
> Nitin
>
> The following changes since commit ee71422b9893f9f77173fb2612d1ffbbc68643c3:
>
>    linux-yocto: allow .cfg, .scc, .patch and defconfigs to be processed in order (2012-04-13 22:44:46 +0100)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib nitin/grub3
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/grub3
>
> Nitin A Kamble (4):
>    eglibc: fix builds on fedora 17 alpha
>    grub-1.99: use gcc-cross for building the target binaries
>    grub-efi-native, grub: fix build with gcc 4.7
>    grub-1.99: fix configure error
>
>   .../grub-1.99-fix-enable_execute_stack-check.patch |   27 ++++
>   .../grub/files/grub-1.99-fpmath-sse-387-fix.patch  |   37 +++++
>   ...rub-1.99-gcc-4.7.0-strict-aliasing-errors.patch |  147 ++++++++++++++++++++
>   ...b-1.99-gcc-4.7.0-uninitialized-var-errors.patch |   41 ++++++
>   .../grub/files/grub-1.99-gcc-4.7.0.patch           |   34 +++++
>   meta/recipes-bsp/grub/grub-efi-native_1.99.bb      |   10 +-
>   meta/recipes-bsp/grub/grub_1.99.bb                 |   10 +-
>   meta/recipes-core/eglibc/eglibc-package.inc        |    5 +
>   meta/recipes-core/eglibc/eglibc_2.13.bb            |    2 +-
>   meta/recipes-core/eglibc/eglibc_2.15.bb            |    2 +-
>   10 files changed, 309 insertions(+), 6 deletions(-)
>   create mode 100644 meta/recipes-bsp/grub/files/grub-1.99-fix-enable_execute_stack-check.patch
>   create mode 100644 meta/recipes-bsp/grub/files/grub-1.99-fpmath-sse-387-fix.patch
>   create mode 100644 meta/recipes-bsp/grub/files/grub-1.99-gcc-4.7.0-strict-aliasing-errors.patch
>   create mode 100644 meta/recipes-bsp/grub/files/grub-1.99-gcc-4.7.0-uninitialized-var-errors.patch
>   create mode 100644 meta/recipes-bsp/grub/files/grub-1.99-gcc-4.7.0.patch
>

Merged into OE-Core with tweaks by RP to the eglibc patch.

Thanks
	Sau!



      parent reply	other threads:[~2012-04-16 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14  8:59 [v2 0/4] grub & eglibc fixes for fedora 17 alpha nitin.a.kamble
2012-04-14  8:59 ` [v2 1/4] eglibc: fix builds on " nitin.a.kamble
2012-04-14 10:14   ` Richard Purdie
2012-04-14 12:27     ` Richard Purdie
2012-04-14  8:59 ` [v2 2/4] grub-1.99: use gcc-cross for building the target binaries nitin.a.kamble
2012-04-14  8:59 ` [v2 3/4] grub-efi-native, grub: fix build with gcc 4.7 nitin.a.kamble
2012-04-14  8:59 ` [v2 4/4] grub-1.99: fix configure error nitin.a.kamble
2012-04-16 15:36 ` Saul Wold [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=4F8C3C8D.3050801@linux.intel.com \
    --to=sgw@linux.intel.com \
    --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