From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] e2fsprogs: fix missing fallocate64() on nios2
Date: Thu, 27 Feb 2014 14:35:47 +0100 [thread overview]
Message-ID: <87ha7kadak.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <52FFB751.1090903@frajasalo.de> (Frank Bergmann's message of "Sat, 15 Feb 2014 19:52:01 +0100")
>>>>> "Frank" == Frank Bergmann <frank@frajasalo.de> writes:
> Nios2 is currently missing the fallocate64 system call. Because of
> compiling the e2fsprogs package with _FILE_OFFSET_BITS=64 the fallocate
> call is replaced by fallocate64 by the glibc. Therefor fallocate is
> entirely disbaled while configuring the package.
> e4defrag have to be disabled because it declares the fallocate64 but
> the library have its own defined.
> It fixes an autobuilder issue:
> http://autobuild.buildroot.org/results/70a/70a47bd7392560cbc1c64769c8357c0b4c91ca3b/
> Signed-off-by: Frank Bergmann <frank@frajasalo.de>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-02-27 13:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-13 Thomas Petazzoni
2014-02-14 9:12 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2014-02-14 10:23 ` Anton Kolesov
2014-02-14 14:13 ` Thomas Petazzoni
2014-02-14 14:42 ` Peter Korsgaard
2014-02-14 15:19 ` Thomas Petazzoni
2014-02-14 17:05 ` Anton Kolesov
2014-02-14 17:42 ` Thomas Petazzoni
2014-02-14 11:29 ` Peter Korsgaard
2014-02-14 13:15 ` Ezequiel García
2014-02-15 7:27 ` Frank Bergmann
2014-02-15 17:29 ` Frank Bergmann
2014-02-15 18:52 ` [Buildroot] [PATCH 1/1] e2fsprogs: fix missing fallocate64() on nios2 Frank Bergmann
2014-02-18 21:19 ` Thomas Petazzoni
2014-02-18 23:13 ` Frank Bergmann
2014-02-20 20:52 ` Frank Bergmann
2014-02-27 13:35 ` Peter Korsgaard [this message]
2014-02-15 21:31 ` [Buildroot] Analysis of build failures Baruch Siach
2014-02-18 21:22 ` [Buildroot] Xtensa support ? Thomas Petazzoni
2014-02-19 0:24 ` Chris Zankel
2014-02-19 8:04 ` Thomas Petazzoni
[not found] ` <CAMo8Bf+gfdgfV+XFows8HmppvXdL=VWXGG_givbUNerep0zeHg@mail.gmail.com>
2014-02-19 13:19 ` Thomas Petazzoni
2014-02-19 5:26 ` Jonathan Ben Avraham
2014-02-19 8:05 ` Thomas Petazzoni
2014-02-19 8:16 ` Jonathan Ben Avraham
2014-02-19 8:22 ` Thomas Petazzoni
2014-02-16 0:00 ` [Buildroot] Analysis of build failures Romain Naour
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=87ha7kadak.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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