From: Khem Raj <raj.khem@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [v2 PATCH 1/8] multilib_header.bbclass: Add oe_multilib_header wrapper
Date: Sat, 30 Jul 2011 10:17:43 -0700 [thread overview]
Message-ID: <1498473.Y2coYvunJ8@perseus> (raw)
In-Reply-To: <547eb0a8ac9c26e8fbc03948a4ebd402c6e9a3fb.1311715727.git.mark.hatle@windriver.com>
On Tuesday, July 26, 2011 04:31:02 PM Mark Hatle wrote:
> This helper function and associated header will allow us to
> resolve two/three header files that conflict due to contents
> that change based on wordsize and ABI.
Will it be a nop for non multilib case ?
next prev parent reply other threads:[~2011-07-30 17:22 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 [this message]
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 ` [v2 PATCH 0/8] Number of multilib related fixes Saul Wold
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=1498473.Y2coYvunJ8@perseus \
--to=raj.khem@gmail.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 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.