From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] fio: disable on nios2 because of missing fallocate64()
Date: Mon, 19 May 2014 22:04:08 +0200 [thread overview]
Message-ID: <87oaytk01z.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1400527410-4637-1-git-send-email-frank@frajasalo.de> (Frank Bergmann's message of "Mon, 19 May 2014 21:23:30 +0200")
>>>>> "Frank" == Frank Bergmann <frank@frajasalo.de> writes:
> The fallocate() function is replaced by fallocate64() while compiling
> with LARGE_FILE flags. Current nios2 toolchain is missing the fallocate64()
> function.
> Signed-off-by: Frank Bergmann <frank@frajasalo.de>
> ---
> Changes v1 -> v2:
> - don't use an architecture-specific patch
> - disable whole package for nios (suggested by Thomas Petazzoni)
> Signed-off-by: Frank Bergmann <frank@frajasalo.de>
> ---
> package/fio/Config.in | 4 ++++
> 1 file changed, 4 insertions(+)
> diff --git a/package/fio/Config.in b/package/fio/Config.in
> index be99f25..5a20b85 100644
> --- a/package/fio/Config.in
> +++ b/package/fio/Config.in
> @@ -12,6 +12,9 @@ config BR2_PACKAGE_FIO
> depends on !BR2_TOOLCHAIN_EXTERNAL_UCLIBC && \
> !BR2_UCLIBC_VERSION_0_9_31 && \
> !BR2_UCLIBC_VERSION_0_9_32
> + # fio uses fallocate() which gets fallocate64() while compiling
> + # with *LARGE_FILE* flags but fallocate64() is not available on nios2
> + depends on !BR2_nios2
Changed *LARGE_FILE* to the Buildroot symbol (BR2_LARGEFILE), added
the autobuilder references as suggested by Yann and committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-05-19 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 19:23 [Buildroot] [PATCH v2 1/1] fio: disable on nios2 because of missing fallocate64() Frank Bergmann
2014-05-19 19:50 ` Yann E. MORIN
2014-05-19 20:04 ` 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=87oaytk01z.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