All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: mfe@pengutronix.de, kernel@pengutronix.de,
	openembedded-core@lists.openembedded.org
Subject: Re: Why do we still disable mke2fs 64bit support?
Date: Mon, 21 Oct 2019 13:24:40 +0300	[thread overview]
Message-ID: <20191021102440.GA25961@localhost> (raw)
In-Reply-To: <20191021094149.uwvkismntthgd7i3@pengutronix.de>

On Mon, Oct 21, 2019 at 11:41:49AM +0200, Marco Felsch wrote:
> Hi,
> 
> during a initial system-setup script the mke2fs tools complains about
> the missing 64bit support:
> 
> 8<----------------------------------------------------------------------
> mke2fs 1.44.5 (15-Dec-2018)
> 64-bit filesystem support is not enabled.  The larger fields afforded by
> this feature enable full-strength checksumming. Pass -O 64bit to rectify.
> 8<----------------------------------------------------------------------
> 
> Other build tools e.g. PTXdist or Buildroot don't modify the build-in
> config. I know in the early days this feature break something but
> shouldn't we (re-)think this decision?

Already fixed in zeus:
https://github.com/openembedded/openembedded-core/commit/f5edce401cfb31ebd0200adaba9a201caf7ea705

> Regards,
>   Marco

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-10-21 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  9:41 Why do we still disable mke2fs 64bit support? Marco Felsch
2019-10-21 10:24 ` Adrian Bunk [this message]
2019-10-21 11:40   ` Marco Felsch
2019-10-24 17:45   ` Tom Rini

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=20191021102440.GA25961@localhost \
    --to=bunk@stusta.de \
    --cc=kernel@pengutronix.de \
    --cc=m.felsch@pengutronix.de \
    --cc=mfe@pengutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    /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.