Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/5] Fix recipe multilib header conflicts
Date: Mon, 25 Jul 2011 14:11:02 -0500	[thread overview]
Message-ID: <4E2DBFC6.70808@windriver.com> (raw)
In-Reply-To: <1311602925.30326.226.camel@phil-desktop>

On 7/25/11 9:08 AM, Phil Blundell wrote:
> On Mon, 2011-07-25 at 14:47 +0100, Richard Purdie wrote:
>> From: Mark Hatle <mark.hatle@windriver.com>
>>
>> Fix the issue where the generated header differs based on the bitsize of the
>> target at the time of building.
>>
>> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
>> ---
>>  meta/recipes-devtools/binutils/binutils.inc        |    4 +++-
>>  .../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 ++++++--
>>  6 files changed, 28 insertions(+), 7 deletions(-)
> 
> The changes in linux-libc-header and linux-libc-headers-yocto don't seem
> to be related to the description above. 

Yes, description is misleading.  The changes to the linux-libc-headers removed a
set of files that had different contents when built for different bitsize.

> Also, the binutils.inc change seems to be missing a PR bump.
> 
> The changes in apr and beecrypt look like they are probably fine, though
> it would be nice for the subject line to mention the names of the
> recipes being changed.

This can be split or kept as a unit.  I kept it as a single unit to show that
these changes are all related.  They don't change the contents of anything --
but resolve conflicts in header files.

--Mark

> p.
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-07-25 19:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 13:47 [PATCH 0/5] Various multilib related fixes Richard Purdie
2011-07-25 13:47 ` [PATCH 1/5] multilib_header.bbclass: Add oe_multilib_header wrapper Richard Purdie
2011-07-25 13:54   ` Phil Blundell
2011-07-25 17:11     ` Mark Hatle
2011-07-25 20:06       ` Phil Blundell
2011-07-26 15:25       ` Mark Hatle
2011-07-25 14:35   ` Phil Blundell
2011-07-25 13:47 ` [PATCH 2/5] Fix recipe multilib header conflicts Richard Purdie
2011-07-25 14:08   ` Phil Blundell
2011-07-25 19:11     ` Mark Hatle [this message]
2011-07-25 13:47 ` [PATCH 3/5] eglibc: Update 2.13 to avoid multilib conflicts Richard Purdie
2011-07-25 13:59   ` Phil Blundell
2011-07-25 19:04     ` Mark Hatle
2011-07-25 20:04       ` Phil Blundell
2011-07-25 13:47 ` [PATCH 4/5] ncurses: Uncompress man pages Richard Purdie
2011-07-25 14:13   ` Phil Blundell
2011-07-25 19:14     ` Mark Hatle
2011-07-25 14:42   ` Enrico Scholz
2011-07-25 15:28     ` Phil Blundell
2011-07-25 13:47 ` [PATCH 5/5] package.bbclass: fixup_perms - symlink bug fix Richard Purdie
2011-07-25 14:05   ` Phil Blundell
2011-07-25 14:14     ` Enrico Scholz
2011-07-25 14:15       ` Phil Blundell
2011-07-25 19:08     ` Mark Hatle
2011-07-25 19:42       ` Phil Blundell

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=4E2DBFC6.70808@windriver.com \
    --to=mark.hatle@windriver.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