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/autobuild: Add ARC glibc fragment
Date: Sat, 21 Oct 2017 22:07:54 +0200	[thread overview]
Message-ID: <20171021220754.0fec8a92@windsurf> (raw)
In-Reply-To: <20171013160909.1408-1-abrodkin@synopsys.com>

Hello,

On Fri, 13 Oct 2017 19:09:09 +0300, Alexey Brodkin wrote:
> glibc is now supported for ARC so let's kick-start autobuilders
> with glibc toolchain for ARC HS.
> 
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> ---
>  support/config-fragments/autobuild/br-arc-full-internal-glibc.config | 4 ++++
>  1 file changed, 4 insertions(+)
>  create mode 100644 support/config-fragments/autobuild/br-arc-full-internal-glibc.config

You forgot to add the toolchain to toolchain-configs.csv, without which
it wouldn't have been taken into account as a possible toolchain for
the autobuilders. Also, the "full" part of the name was only meant for
uclibc to indicate that "all uClibc options" were enabled. For a glibc
toolchain, it din't make sense, so I dropped this part of the file name.

I'd prefer to have an external toolchain for this configuration rather
than rebuild over and over again that toolchain. But we can do this
once we have such a toolchain available on
http://toolchains.free-electrons.com.

Thanks!

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

      reply	other threads:[~2017-10-21 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 16:09 [Buildroot] [PATCH] support/config-fragments/autobuild: Add ARC glibc fragment Alexey Brodkin
2017-10-21 20:07 ` 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=20171021220754.0fec8a92@windsurf \
    --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