From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] e2fsprogs: fix missing fallocate64() on nios2
Date: Thu, 27 Feb 2014 14:36:41 +0100 [thread overview]
Message-ID: <87a9dcad92.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1392933578-2256-1-git-send-email-frank@frajasalo.de> (Frank Bergmann's message of "Thu, 20 Feb 2014 22:59:37 +0100")
>>>>> "Frank" == Frank Bergmann <frank@frajasalo.de> writes:
> (external) nios2 toolchain is currently missing the fallocate64 system
> call. Because of compiling the e2fsprogs package with _FILE_OFFSET_BITS=64,
> _LARGEFILE_SOURCE and _LARGEFILE64_SOURCE the fallocate call is replaced
> by fallocate64 by the glibc. Therefore fallocate is entirely disabled while
> configuring the package.
> Fixes http://autobuild.buildroot.org/results/70a/70a47bd7392560cbc1c64769c8357c0b4c91ca3b/
Ups, this was the one I committed, not v1.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-02-27 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 21:59 [Buildroot] [PATCH v2 1/2] e2fsprogs: fix missing fallocate64() on nios2 Frank Bergmann
2014-02-20 21:59 ` [Buildroot] [PATCH v2 2/2] e2fsprogs: disable e4defrag for nios Frank Bergmann
2014-02-27 13:36 ` Peter Korsgaard
2014-02-27 13:36 ` Peter Korsgaard [this message]
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=87a9dcad92.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