From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [FYI] Bootlin external toolchains
Date: Tue, 3 Dec 2019 14:57:42 +0100 [thread overview]
Message-ID: <20191203145742.2d3a5af3@windsurf> (raw)
In-Reply-To: <CAMw6YJL=DREwg6HM-xnijK=nhxJGaf4P_Jga+46W2jGBMqmE3g@mail.gmail.com>
Hello,
On Tue, 3 Dec 2019 13:06:18 +0200
Vadim Kochan <vadim4j@gmail.com> wrote:
> > Such fragments already exist for each toolchain, for example:
> >
> > https://toolchains.bootlin.com/downloads/releases/toolchains/aarch64/fragments/aarch64--glibc--stable-2018.11-1.frag
> >
>
> Yes, I already used them) I meant, it would be good to have such
> script in Buildroot which allows to generate such fragments for any
> toolchain.
Well, the script you're talking about, and the script that generates
the above fragment are very different.
The fragment above is generated together with the toolchain, when we
know what is the Buildroot configuration used to build the toolchain.
If I understand correctly, what you propose is instead a script that
given some random toolchain (generated by Buildroot, crosstool-ng, or
any other mean), will output a snippet of Buildroot configuration that
matches this toolchain.
We did have such a proposal some time ago on the mailing list, and
there was some discussion around it. I can't remember if it was
abandoned because nobody cared enough, or because there were some real
technical issues. Unfortunately, I was not able to quickly locate the
patch I'm talking about :-/
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-03 13:57 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 [this message]
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
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=20191203145742.2d3a5af3@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