Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/5] eglibc: Update 2.13 to avoid multilib conflicts
Date: Mon, 25 Jul 2011 14:59:38 +0100	[thread overview]
Message-ID: <1311602379.30326.220.camel@phil-desktop> (raw)
In-Reply-To: <f654f647aa04b5173883785af5cb062df676842a.1311601422.git.richard.purdie@linuxfoundation.org>

On Mon, 2011-07-25 at 14:47 +0100, Richard Purdie wrote:
> --- /dev/null
> +++ b/meta/recipes-core/eglibc/eglibc-2.13/arch-ia32.patch
> @@ -0,0 +1,5309 @@
> +Sync the i386 and x86_64 headers into one common IA32 set of headers.
> +
> +The goal is to ensure that any headers produced in a 32-bit or 64-bit build
> +are not only functionally equivalent, but actually the same in order to avoid
> +file conflicts.
> +
> +The only remaining conflict is the bits/syscall.h.  This is dynamically
> +generated, and so far I've been unable to figure out how to get both
> +i386 and x86_64 to generate the same file.  We'll need to handle this
> +in the recipe itself.
> +
> +Signed-off-by: Mark Hatle <mark.hatle@windriver.com>

This patch is missing an Upstream-Status.  It's also rather large and
intrusive which makes it hard to review sensibly and seems like it might
be a maintenance headache in the future.  I wonder whether it would be
better to just put the 32-bit and 64-bit headers for eglibc in separate
subdirectories (say /usr/include/32/... and /usr/include/64/...) and not
bother even trying to patch them to be the same.

p.





  reply	other threads:[~2011-07-25 14:03 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
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 [this message]
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=1311602379.30326.220.camel@phil-desktop \
    --to=philb@gnu.org \
    --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