All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-architecture
	<openembedded-architecture@lists.openembedded.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] [PATCH] meta: start to ignore the largefile distro feature
Date: Tue, 7 Mar 2017 18:34:42 -0800	[thread overview]
Message-ID: <20170308023441.GA28127@haswell> (raw)
In-Reply-To: <CAJTo0LaNUQW=Qsyxm7eC9hFduzVMy5v+1Sy9aBMfgNoBgAqoow@mail.gmail.com>

On 17-03-07 10:35:58, Burton, Ross wrote:
> CCing openembedded-architecture to open the field for comments.
> 
> On 7 March 2017 at 04:58, Andre McCurdy <armccurdy@gmail.com> wrote:
> 
> > The largefile distro feature has been enabled by default in oe-core
> > for a long time and, more recently, also in poky-tiny. Building
> > without the largefile distro feature receives little or no testing.
> > Many packages now enable LFS without exposing a configure option, so
> > there should be very little expectation that disabling the distro
> > feature will result in a distro which globally disables LFS.
> >
> 
> So I've had a bug for this for some time but have never got around to it.
> 
> If we're going to assert "LFS by default" do we want a sanity check to
> verify it was used?
> 
> Do we want to put -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 in the default
> CFLAGS?

I think this is fine to assert, however, there might be applications which
still want to use --enable/--disable autoconf stuff, and ignore/override the
env settings we might pass, so we need to watch
out for those. Otherwise, this seems a step in right direction.

> 
> I'm not aware of any good reason to not use LFS, but now is the time for
> anyone else to speak up if you have a good reason to keep it as an option!

me neither, we should just make it default settings.

> 
> Ross

> _______________________________________________
> Openembedded-architecture mailing list
> Openembedded-architecture@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture



      parent reply	other threads:[~2017-03-08  2:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07  4:58 [PATCH] meta: start to ignore the largefile distro feature Andre McCurdy
2017-03-07 10:35 ` Burton, Ross
2017-03-07 14:43   ` [Openembedded-architecture] " Mark Hatle
2017-03-07 14:45     ` Burton, Ross
2017-03-08  7:12       ` Josef Holzmayr
2017-03-07 20:49     ` Richard Purdie
2017-03-07 17:05   ` Burton, Ross
2017-03-08  2:34   ` Khem Raj [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=20170308023441.GA28127@haswell \
    --to=raj.khem@gmail.com \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.