From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [v2 PATCH 0/8] Number of multilib related fixes
Date: Wed, 27 Jul 2011 17:41:37 -0700 [thread overview]
Message-ID: <4E30B041.7060801@linux.intel.com> (raw)
In-Reply-To: <cover.1311715727.git.mark.hatle@windriver.com>
On 07/26/2011 02:31 PM, Mark Hatle wrote:
> Fix a number of multilib issues include IA32 eglibc header generation,
> misc header conflicts and ncurses man page collisions.
>
> This is v2 of the patch set, original was sent by Richard.
>
> The following changes since commit dad2169cfb331b7af5c6d380347ea279a59bd716:
>
> classes/image_types: IMAGE_TYPES was missing some entries (2011-07-26 15:52:40 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib mhatle/ml_fixes
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/ml_fixes
>
> Mark Hatle (8):
> multilib_header.bbclass: Add oe_multilib_header wrapper
> binutils: Fix multilib header conflict - bfd.h
> apr: Fix multilib header conflict - apr.h
> beecrypt: Fix multilib header conflict - beecrypt/gnu.h
> linux-libc-headers: Fix file conflict -- ..install.cmd
> eglibc_2.13: Resolve multilib header conflicts
> ncurses: Resolve header and man page multilib conflicts
> package.bbclass: fixup_perms - change symlink processing
>
> meta/classes/multilib_header.bbclass | 29 ++++++
> meta/classes/package.bbclass | 10 +-
> meta/recipes-core/eglibc/eglibc-package.inc | 4 +-
> meta/recipes-core/eglibc/eglibc_2.13.bb | 91 ++++++++++++++++++++
> meta/recipes-core/ncurses/ncurses.inc | 7 +-
> meta/recipes-devtools/binutils/binutils.inc | 4 +-
> meta/recipes-devtools/binutils/binutils_2.21.1.bb | 2 +-
> .../linux-libc-headers-yocto_git.bb | 5 +-
> .../linux-libc-headers_2.6.37.2.bb | 5 +-
> .../linux-libc-headers_2.6.39.bb | 5 +
> meta/recipes-support/apr/apr_1.4.2.bb | 8 ++-
> meta/recipes-support/beecrypt/beecrypt_4.2.1.bb | 8 ++-
> scripts/multilib_header_wrapper.h | 55 ++++++++++++
> 13 files changed, 217 insertions(+), 16 deletions(-)
> create mode 100644 meta/classes/multilib_header.bbclass
> create mode 100644 scripts/multilib_header_wrapper.h
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-07-28 0:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 21:31 [v2 PATCH 0/8] Number of multilib related fixes Mark Hatle
2011-07-26 21:31 ` [v2 PATCH 1/8] multilib_header.bbclass: Add oe_multilib_header wrapper Mark Hatle
2011-07-30 17:17 ` Khem Raj
2011-07-26 21:31 ` [v2 PATCH 2/8] binutils: Fix multilib header conflict - bfd.h Mark Hatle
2011-07-26 21:31 ` [v3 PATCH 3/8] apr: Fix multilib header conflict - apr.h Mark Hatle
2011-07-26 21:31 ` [v2 PATCH 4/8] beecrypt: Fix multilib header conflict - beecrypt/gnu.h Mark Hatle
2011-07-26 21:31 ` [v2 PATCH 5/8] linux-libc-headers: Fix file conflict -- ..install.cmd Mark Hatle
2011-07-27 12:09 ` Andrea Adami
2011-07-26 21:31 ` [v2 PATCH 6/8] eglibc_2.13: Resolve multilib header conflicts Mark Hatle
2011-07-26 21:31 ` [v2 PATCH 7/8] ncurses: Resolve header and man page multilib conflicts Mark Hatle
2011-07-26 21:31 ` [v2 PATCH 8/8] package.bbclass: fixup_perms - change symlink processing Mark Hatle
2011-07-28 0:41 ` 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=4E30B041.7060801@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