From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [FYI] Bootlin external toolchains
Date: Mon, 9 Dec 2019 16:59:22 +0100 [thread overview]
Message-ID: <20191209165922.335b2af1@windsurf> (raw)
In-Reply-To: <09654893-fe44-76f0-da65-3f29bc758c6f@mind.be>
Hello,
On Tue, 3 Dec 2019 22:15:47 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> To kick off the bikeshedding, here's my opinion on what the package should look
> like.
>
> * It should be a single package, toolchain-external-bootlin. Maybe two (-stable
> and -bleeding-edge) but I think there'll be enough shared infrastructure to
> warrant creating a single package.
Agreed. My initial start of work in this area looked exactly like this:
a single package. See
https://github.com/tpetazzoni/buildroot/commit/58413ab16c6b203dca48db182e74e59ae73c958a.
Note: this commit is far from being something that works. If I had
something that worked, I would have submitted it.
> * It should offer a choice in Config.in.options for libc and stable/bleeding-edge.
See commit above :-)
> * For now, it should be limited to *exactly* the same architecture suboptions as
> what the toolchain was built for. Later we can decide how to expand this to
> compatible options (e.g. the core-i7 toolchain will also work for core-avx2) -
> but I'm pretty sure that that is something that will require help from
> toolchain-builder itself.
Pretty much what I did, yes :-)
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-12-09 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 0:47 [Buildroot] [FYI] Bootlin external toolchains Vadim Kochan
2019-12-02 14:26 ` Thomas Petazzoni
2019-12-03 9:59 ` Romain Naour
2019-12-03 10:07 ` Vadim Kochan
2019-12-03 11:00 ` Thomas Petazzoni
2019-12-03 11:06 ` Vadim Kochan
2019-12-03 13:57 ` Thomas Petazzoni
2019-12-03 20:52 ` Arnout Vandecappelle
2019-12-03 21:15 ` Arnout Vandecappelle
2019-12-04 21:52 ` Romain Naour
2019-12-09 23:04 ` Arnout Vandecappelle
2019-12-09 15:59 ` 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=20191209165922.335b2af1@windsurf \
--to=thomas.petazzoni@bootlin.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