From: Graham Gower <graham.gower@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] e2fsprogs_1.41.9.bb: Fix build for uclibc when DISTRO_FEATURES lacks largefile.
Date: Wed, 01 Dec 2010 13:31:40 +1030 [thread overview]
Message-ID: <4CF5BA94.1020007@gmail.com> (raw)
CC llseek.c
llseek.c:65:22: error: expected declaration specifiers or '...' before '_llseek'
llseek.c:65:43: error: expected declaration specifiers or '...' before 'fd'
llseek.c:65:60: error: expected declaration specifiers or '...' before 'offset_high'
llseek.c:66:19: error: expected declaration specifiers or '...' before 'offset_low'
llseek.c:66:44: error: expected declaration specifiers or '...' before 'result'
llseek.c:67:18: error: expected declaration specifiers or '...' before 'origin'
llseek.c: In function '_syscall5':
llseek.c:71:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
llseek.c:91:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
llseek.c:65:1: error: parameter name omitted
llseek.c:65:22: error: parameter name omitted
llseek.c:65:43: error: parameter name omitted
llseek.c:66:4: error: parameter name omitted
llseek.c:66:19: error: parameter name omitted
llseek.c:67:4: error: parameter name omitted
llseek.c:114:1: error: expected '{' at end of input
make[2]: *** [llseek.o] Error 1
Signed-off-by: Graham Gower <graham.gower@gmail.com>
---
.../e2fsprogs/e2fsprogs-1.41.9/llseek-uclibc.patch | 24 ++++++++++++++++++++
recipes/e2fsprogs/e2fsprogs_1.41.9.bb | 4 ++-
2 files changed, 27 insertions(+), 1 deletions(-)
create mode 100644 recipes/e2fsprogs/e2fsprogs-1.41.9/llseek-uclibc.patch
diff --git a/recipes/e2fsprogs/e2fsprogs-1.41.9/llseek-uclibc.patch b/recipes/e2fsprogs/e2fsprogs-1.41.9/llseek-uclibc.patch
new file mode 100644
index 0000000..026db2a
--- /dev/null
+++ b/recipes/e2fsprogs/e2fsprogs-1.41.9/llseek-uclibc.patch
@@ -0,0 +1,24 @@
+diff -ur e2fsprogs-1.41.9.orig/lib/blkid/llseek.c e2fsprogs-1.41.9/lib/blkid/llseek.c
+--- e2fsprogs-1.41.9.orig/lib/blkid/llseek.c 2009-08-13 11:09:57.000000000 +0930
++++ e2fsprogs-1.41.9/lib/blkid/llseek.c 2010-12-01 13:23:48.000000000 +1030
+@@ -28,7 +28,7 @@
+
+ #include "blkidP.h"
+
+-#ifdef __linux__
++#if defined(__linux__) && !(defined(__UCLIBC__) && !defined(__USE_FILE_OFFSET64))
+
+ #if defined(HAVE_LSEEK64) && defined(HAVE_LSEEK64_PROTOTYPE)
+
+diff -ur e2fsprogs-1.41.9.orig/lib/ext2fs/llseek.c e2fsprogs-1.41.9/lib/ext2fs/llseek.c
+--- e2fsprogs-1.41.9.orig/lib/ext2fs/llseek.c 2009-08-13 11:09:57.000000000 +0930
++++ e2fsprogs-1.41.9/lib/ext2fs/llseek.c 2010-12-01 13:18:26.000000000 +1030
+@@ -28,7 +28,7 @@
+ #include "et/com_err.h"
+ #include "ext2fs/ext2_io.h"
+
+-#ifdef __linux__
++#if defined(__linux__) && !(defined(__UCLIBC__) && !defined(__USE_FILE_OFFSET64))
+
+ #if defined(HAVE_LSEEK64) && defined(HAVE_LSEEK64_PROTOTYPE)
+
diff --git a/recipes/e2fsprogs/e2fsprogs_1.41.9.bb b/recipes/e2fsprogs/e2fsprogs_1.41.9.bb
index 6a8c113..026e35a 100644
--- a/recipes/e2fsprogs/e2fsprogs_1.41.9.bb
+++ b/recipes/e2fsprogs/e2fsprogs_1.41.9.bb
@@ -1,6 +1,8 @@
require e2fsprogs.inc
-PR = "${INC_PR}"
+PR = "${INC_PR}.1"
+
+SRC_URI += "file://llseek-uclibc.patch"
do_configure() {
oe_runconf
--
1.7.1
reply other threads:[~2010-12-01 3:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CF5BA94.1020007@gmail.com \
--to=graham.gower@gmail.com \
--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 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.