From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] arch: add option to disable internal toolchain backend
Date: Sat, 2 Sep 2017 22:17:58 +0200 [thread overview]
Message-ID: <20170902221758.284de319@windsurf.lan> (raw)
In-Reply-To: <20170902201010.GD3396@scaer>
Hello,
On Sat, 2 Sep 2017 22:10:10 +0200, Yann E. MORIN wrote:
> > I'm not a big fan of the option name. What about:
>
> Oh, neither am I, neither am I. You know well that I am very bad at
> finding good names. ;-)
No problem, that's what reviews are made for!
> > So, arches can select BR2_ARCH_HAS_NO_TOOLCHAIN_BUILDROOT, and else
> > we can "depends on BR2_ARCH_HAS_TOOLCHAIN_BUILDROOT".
>
> I also thought about doing so, yes, but is it really necessary to
> introduce two blind options just to have a positive logic in the only
> location we need it?
Yeah, I also thought about this. It's true that the positive symbol is
going to be used only in one place, and it's the negative symbol (the
one being selected) that will be used in most places.
So perhaps you're right, and having both hidden booleans is not that
useful.
> > Now that I think of it: we have dropped the Blackfin ADI external
> > toolchain. Therefore, we currently have no in-tree solution to use/test
> > bf606, bf607, bf608, etc. Perhaps we should drop them instead ?
>
> As already said: I don;t care about bfin, so I'm fine with dropping
> those bfin cores. But we'd still need BR2_ARCH_HAS_TOOLCHAIN_BUILDROOT
> and BR2_ARCH_HAS_NO_TOOLCHAIN_BUILDROOT for the rest, no?
Yes, we would still need them. I'm not at all saying that your patch
series is not useful, I'm just saying that for Blackfin, dropping
support for those cores is better :)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-02 20:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 19:38 [Buildroot] [PATCH 0/4] arch: not all have support in the internal backend Yann E. MORIN
2017-09-02 19:38 ` [Buildroot] [PATCH 1/4] arch: add option to disable internal toolchain backend Yann E. MORIN
2017-09-02 19:47 ` Thomas Petazzoni
2017-09-02 20:10 ` Yann E. MORIN
2017-09-02 20:17 ` Thomas Petazzoni [this message]
2017-09-02 19:38 ` [Buildroot] [PATCH 2/4] arch/csky: internal backend not suitable Yann E. MORIN
2017-09-02 19:38 ` [Buildroot] [PATCH 3/4] arch/bfin: internal backend not suitable for some cores Yann E. MORIN
2017-09-02 19:48 ` Thomas Petazzoni
2017-09-02 20:01 ` Yann E. MORIN
2017-09-02 19:38 ` [Buildroot] [PATCH 4/4] arch/mips: " Yann E. MORIN
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=20170902221758.284de319@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