From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Romain Naour <romain.naour@gmail.com>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] Arc and C-Sky toolchains
Date: Fri, 10 Sep 2021 17:18:15 +0200 [thread overview]
Message-ID: <20210910171815.6d6d00ea@windsurf> (raw)
In-Reply-To: <e465a48d-f2eb-6822-415b-06468a375fce@benettiengineering.com>
On Wed, 8 Sep 2021 23:29:07 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> I can't understand the reason why Arc and C-Sky provide a special
> toolchain(i.e. synopsis gcc10) instead of treating them like external
> toolchains. Can you help me in understanding this?
You're confusing things here.
ARC and C-SKY support is (was for ARC) not in upstream
gcc/binutils/gdb, so we have (had) to use specific forks of these
projects, that have support for those CPU architectures.
This is completely independent from the ability to use external
toolchains for those CPU architectures.
An external toolchain is a pre-compiled toolchain. Here what we want is
support for ARC and C-SKY in our internal toolchain backend, where
Buildroot builds gcc/binutils/gdb/libc.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-10 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 21:29 [Buildroot] Arc and C-Sky toolchains Giulio Benetti
2021-09-08 21:45 ` Giulio Benetti
2021-09-10 15:18 ` Thomas Petazzoni [this message]
2021-09-10 19:43 ` Giulio Benetti
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=20210910171815.6d6d00ea@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox