From: Hollis Blanchard <hollis_blanchard@mentor.com>
To: buildroot@busybox.net
Subject: [Buildroot] building host-e2fsprogs on RHEL5.8
Date: Tue, 28 Jul 2015 17:23:58 -0700 [thread overview]
Message-ID: <55B81D1E.90203@mentor.com> (raw)
I get two errors when building buildroot's host-e2fsprogs (1.42.13) on
RHEL5.8, both from e4defrag.c:
e4defrag.c:197:2: error: #error sync_file_range not available!
e4defrag.c:201:2: error: #error fallocate64 not available!
The latter can be patched by calling posix_fallocate64 instead. The
former seems to be due to a known bug
<https://bugzilla.redhat.com/show_bug.cgi?id=518581>, requiring manually
calling syscall().
(For the record, this is glibc 2.5 and kernel 2.6.18.)
I can work around the problem with this:
diff --git a/package/e2fsprogs/e2fsprogs.mk b/package/e2fsprogs/e2fsprogs.mk
index 0537521..4aeda83 100644
--- a/package/e2fsprogs/e2fsprogs.mk
+++ b/package/e2fsprogs/e2fsprogs.mk
@@ -12,6 +12,9 @@ E2FSPROGS_LICENSE_FILES = COPYING lib/uuid/COPYING
lib/ss/mit-sipb-copyright.h l
E2FSPROGS_INSTALL_STAGING = YES
E2FSPROGS_INSTALL_STAGING_OPTS = DESTDIR=$(STAGING_DIR) install-libs
+HOST_E2FSPROGS_CONF_OPTS = \
+ --disable-defrag
+
E2FSPROGS_CONF_OPTS = \
$(if $(BR2_STATIC_LIBS),,--enable-elf-shlibs) \
$(if $(BR2_PACKAGE_E2FSPROGS_DEBUGFS),,--disable-debugfs) \
Alternately, if I come up with patches to work around these two
problems, would buildroot carry them until upstream e2fsprogs (hopefully
one day) picks them up?
--
Hollis Blanchard
Mentor Graphics Emulation Division
next reply other threads:[~2015-07-29 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 0:23 Hollis Blanchard [this message]
2015-07-29 7:06 ` [Buildroot] building host-e2fsprogs on RHEL5.8 Thomas Petazzoni
2015-07-29 15:38 ` Hollis Blanchard
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=55B81D1E.90203@mentor.com \
--to=hollis_blanchard@mentor.com \
--cc=buildroot@busybox.net \
/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