Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] glibc 2.7 and 2.9 (arm): Remove unnecessary asm/page.h include
Date: Mon, 17 Aug 2009 14:53:00 +0100	[thread overview]
Message-ID: <4A8960BC.4000603@cam.ac.uk> (raw)

Fix compile bug for arm with recent kernel headers
../ports/sysdeps/unix/sysv/linux/arm/ioperm.c:48:22: error: asm/page.h: No such file or directory

Signed-off-by: Jonathan Cameron <jic23@cam.ac.uk>
---
Update to previous posting under 
[PATCH] glibc 2.9: Remove unnecessary asm/page.h include, not present in recent headers

This patch is already included by the 2.6.1 recipe (thanks Khem)
Prevents the following error with recent kernel headers
../ports/sysdeps/unix/sysv/linux/arm/ioperm.c:48:22: error: asm/page.h: No such file or directory

Fixes problem with 2.6.29 headers against both glibc 2.7 and 2.9

Related bug reports (with equivalent solutions)
http://www.mail-archive.com/debian-glibc@lists.debian.org/msg38393.html
http://sourceware.org/ml/crossgcc/2008-05/msg00014.html
http://sourceware.org/ml/libc-ports/2008-04/msg00005.html

Bug no longer exists at head of glibc ports tree. May effect other versions.

 recipes/glibc/glibc_2.7.bb |    3 ++-
 recipes/glibc/glibc_2.9.bb |    3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/recipes/glibc/glibc_2.7.bb b/recipes/glibc/glibc_2.7.bb
index f152756..dcea69c 100644
--- a/recipes/glibc/glibc_2.7.bb
+++ b/recipes/glibc/glibc_2.7.bb
@@ -5,7 +5,7 @@ ARM_INSTRUCTION_SET = "arm"
 PACKAGES_DYNAMIC = "libc6*"
 RPROVIDES_${PN}-dev = "libc6-dev virtual-libc-dev"
 
-PR = "${INC_PR}.0"
+PR = "${INC_PR}.1"
 
 # the -isystem in bitbake.conf screws up glibc do_stage
 BUILD_CPPFLAGS = "-I${STAGING_INCDIR_NATIVE}"
@@ -68,6 +68,7 @@ SRC_URI = "ftp://ftp.gnu.org/pub/gnu/glibc/glibc-${PV}.tar.bz2 \
            file://etc/ld.so.conf \
            file://generate-supported.mk \
            file://march-i686.patch;patch=1;pnum=0 \
+	   file://glibc-arm-no-asm-page.patch;patch=1 \
            "
 
 
diff --git a/recipes/glibc/glibc_2.9.bb b/recipes/glibc/glibc_2.9.bb
index 6e323aa..9849c0a 100644
--- a/recipes/glibc/glibc_2.9.bb
+++ b/recipes/glibc/glibc_2.9.bb
@@ -5,7 +5,7 @@ ARM_INSTRUCTION_SET = "arm"
 PACKAGES_DYNAMIC = "libc6*"
 RPROVIDES_${PN}-dev = "libc6-dev virtual-libc-dev"
 
-PR = "${INC_PR}.0"
+PR = "${INC_PR}.1"
 
 # the -isystem in bitbake.conf screws up glibc do_stage
 BUILD_CPPFLAGS = "-I${STAGING_INCDIR_NATIVE}"
@@ -65,6 +65,7 @@ SRC_URI = "ftp://ftp.gnu.org/pub/gnu/glibc/glibc-${PV}.tar.bz2 \
            file://generate-supported.mk \
            file://march-i686.patch;patch=1;pnum=0 \
 	   file://tls_i486.patch;patch=1 \
+	   file://glibc-arm-no-asm-page.patch;patch=1 \
            "
 
 
-- 
1.6.3.3




             reply	other threads:[~2009-08-17 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 13:53 Jonathan Cameron [this message]
2009-08-17 14:06 ` [PATCH] glibc 2.7 and 2.9 (arm): Remove unnecessary asm/page.h include Holger Hans Peter Freyther
2009-08-17 15:01   ` Phil Blundell
2009-08-17 15:02     ` Phil Blundell
2009-08-18  9:06       ` Otavio Salvador
2009-08-19 11:06         ` Jonathan Cameron
2009-08-18 13:26   ` Jonathan Cameron

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=4A8960BC.4000603@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=openembedded-devel@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