All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Bergmann <frank@frajasalo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] e2fsprogs: fix missing fallocate64() on nios2
Date: Thu, 20 Feb 2014 21:52:34 +0100	[thread overview]
Message-ID: <53066B12.2030107@frajasalo.de> (raw)
In-Reply-To: <5303E913.2080701@frajasalo.de>

Hello,

On 19.02.2014 00:13, Frank Bergmann wrote:
> On 18.02.2014 22:19, Thomas Petazzoni wrote:
>>> diff --git a/package/e2fsprogs/Config.in b/package/e2fsprogs/Config.in
>>> index 7775e94..1e87aef 100644
>>> --- a/package/e2fsprogs/Config.in
>>> +++ b/package/e2fsprogs/Config.in
>>> @@ -49,7 +49,7 @@ config BR2_PACKAGE_E2FSPROGS_E2UNDO
>>>
>>>    config BR2_PACKAGE_E2FSPROGS_E4DEFRAG
>>>           bool "e4defrag"
>>> -       depends on !BR2_avr32 # fallocate not implemented
>>> +       depends on !BR2_avr32 && !BR2_nios2 # fallocate not implemented
>>>
>>>    config BR2_PACKAGE_E2FSPROGS_FILEFRAG
>>>           bool "filefrag"
>>> diff --git a/package/e2fsprogs/e2fsprogs.mk b/package/e2fsprogs/e2fsprogs.mk
>>> index 2eb59f5..310f549 100644
>>> --- a/package/e2fsprogs/e2fsprogs.mk
>>> +++ b/package/e2fsprogs/e2fsprogs.mk
>>> @@ -23,7 +23,8 @@ E2FSPROGS_CONF_OPT = \
>>>           --disable-libuuid \
>>>           --enable-fsck \
>>>           --disable-e2initrd-helper \
>>> -       --disable-testio-debug
>>> +       --disable-testio-debug \
>>> +       $(if $(BR2_nios2),ac_cv_func_fallocate=no,)
>>
>> Such variables are normally passed in <pkg>_CONF_ENV. Also, in
>> Config.in, the fallocate problem seems to also apply for AVR32, while
>> you only pass ac_cv_func_fallocate=no for NIOS II here. Could you
>> explain why?
>
> As written in the patch description fallocate is replaced by fallocate64 if using
> _FILE_OFFSET_BITS=64 . fallocate64 is not available in nios2 toolchain library. So
> if in that case we want to avoid fallocate64 then we have to avoid fallocate.
>
> Not sure for the moment why it's working for AVR32 but fallocate is referenced in
> lib/ext2fs/unix_io.c which builds libext2fs.so and therefore it's independent of
> e4defrag. Only avoiding e4defrag does not work for nios2.

On AVR32 there is neither fallocate nor fallocate64 available. e4defrag has to be
disabled on this architecture because it uses the fallocate system call which is
also not available.

Frank.

  reply	other threads:[~2014-02-20 20:52 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 [this message]
2014-02-27 13:35         ` Peter Korsgaard
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=53066B12.2030107@frajasalo.de \
    --to=frank@frajasalo.de \
    --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 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.