Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/config-fragments: linaro-arm: remove default option
Date: Fri, 12 Jan 2018 22:25:28 +0100	[thread overview]
Message-ID: <20180112222528.15c247e9@windsurf.lan> (raw)
In-Reply-To: <20180109225407.24501-1-romain.naour@gmail.com>

Hello,

On Tue,  9 Jan 2018 23:54:05 +0100, Romain Naour wrote:
> Remove BR2_ARM_EABIHF and BR2_TOOLCHAIN_EXTERNAL_LINARO_ARM which are
> used by default when a cortex-A8 CPU is used.
> 
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
>  support/config-fragments/autobuild/linaro-arm.config | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/support/config-fragments/autobuild/linaro-arm.config b/support/config-fragments/autobuild/linaro-arm.config
> index d72e19b3ad..0f9b687d7a 100644
> --- a/support/config-fragments/autobuild/linaro-arm.config
> +++ b/support/config-fragments/autobuild/linaro-arm.config
> @@ -1,5 +1,3 @@
>  BR2_arm=y
>  BR2_cortex_a8=y
> -BR2_ARM_EABIHF=y
>  BR2_TOOLCHAIN_EXTERNAL=y
> -BR2_TOOLCHAIN_EXTERNAL_LINARO_ARM=y

I am not convinced about removing BR2_TOOLCHAIN_EXTERNAL_LINARO_ARM.
Indeed, we may very well add another external toolchain in the future
for ARM EABIhf. But since this defconfig is named linaro-arm, it really
should test the Linaro ARM toolchain, so it makes sense to have this
explicit option.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      parent reply	other threads:[~2018-01-12 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 22:54 [Buildroot] [PATCH] support/config-fragments: linaro-arm: remove default option Romain Naour
2018-01-09 22:54 ` [Buildroot] [PATCH] support/config-fragments: linaro-aarch64: " Romain Naour
2018-01-09 22:54 ` [Buildroot] [PATCH] support/config-fragments: br-powerpc-internal-full: remove old option Romain Naour
2018-01-12 21:26   ` Thomas Petazzoni
2018-01-12 21:25 ` Thomas Petazzoni [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=20180112222528.15c247e9@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --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