All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 04/15] toolchain: remove LARGEFILE selects
Date: Tue, 17 Mar 2015 12:11:49 -0300	[thread overview]
Message-ID: <55084435.6050806@zacarias.com.ar> (raw)
In-Reply-To: <20150314223621.GI4009@free.fr>

On 03/14/2015 07:36 PM, Yann E. MORIN wrote:

> Gustavo, All,
> 
> On 2015-03-13 15:22 -0300, Gustavo Zacarias spake thusly:
>> There's no need for toolchains or the user to declare largefile support
>> since it's now mandatory.
> 
> With the new patch I suggested you had before patch 3, do not forget to
> also remove the select from BR2_TOOLCHAIN_BUILDROOT_LARGEFILE in this
> patch.
> 
> Regards,
> Yann E. MORIN.

The only place where BR2_TOOLCHAIN_BUILDROOT_LARGEFILE is selected/used
is in defconfigs, so there's no need for anything additional in this
patch (that's handled in patch 8).
Regards.

  reply	other threads:[~2015-03-17 15:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 18:21 [Buildroot] [PATCH 00/15] Drop non-largefile support Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 01/15] toolchain/helpers: add mandatory check for uclibc toolchain options Gustavo Zacarias
2015-03-14 22:18   ` Yann E. MORIN
2015-03-17 12:18     ` Gustavo Zacarias
2015-03-17 14:13     ` Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 02/15] toolchain/helpers: make LFS mandatory for uclibc Gustavo Zacarias
2015-03-14 22:22   ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 03/15] toolchain-common: default to Y for LARGEFILE Gustavo Zacarias
2015-03-14 22:34   ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 04/15] toolchain: remove LARGEFILE selects Gustavo Zacarias
2015-03-14 22:36   ` Yann E. MORIN
2015-03-17 15:11     ` Gustavo Zacarias [this message]
2015-03-13 18:22 ` [Buildroot] [PATCH 05/15] gcc/final: drop non-lfs builds Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 06/15] package infra: drop non-lfs support Gustavo Zacarias
2015-03-14 22:46   ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 07/15] package/uclibc: drop non-largefile support Gustavo Zacarias
2015-03-14 22:47   ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 08/15] configs: drop largefile option Gustavo Zacarias
2015-03-14 22:47   ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 09/15] busybox: force lfs build Gustavo Zacarias
2015-03-14 22:49   ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 10/15] system: drop largefile depends Gustavo Zacarias
2015-03-14 22:50   ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 11/15] boot/gummiboot: " Gustavo Zacarias
2015-03-14 22:52   ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 12/15] packages: remove (non-)lfs dependencies and tweaks Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 13/15] toolchain-common: drop BR2_LARGEFILE Gustavo Zacarias
2015-03-14 22:53   ` Yann E. MORIN
2015-03-13 18:22 ` [Buildroot] [PATCH 14/15] packages: remove non-lfs enabler patches Gustavo Zacarias
2015-03-13 18:22 ` [Buildroot] [PATCH 15/15] docs/manual: remove references to largefile Gustavo Zacarias
2015-03-14 22:56   ` Yann E. MORIN
2015-03-14 22:58 ` [Buildroot] [PATCH 00/15] Drop non-largefile support Yann E. MORIN
2015-03-17 12:23   ` Gustavo Zacarias

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=55084435.6050806@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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.