From: Vadim Kochan <vadim4j@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [FYI] Bootlin external toolchains
Date: Tue, 3 Dec 2019 13:06:18 +0200 [thread overview]
Message-ID: <CAMw6YJL=DREwg6HM-xnijK=nhxJGaf4P_Jga+46W2jGBMqmE3g@mail.gmail.com> (raw)
In-Reply-To: <20191203120029.2962bfaa@windsurf>
Hi Thomas, All
On Tue, Dec 3, 2019 at 1:00 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> On Tue, 3 Dec 2019 12:07:51 +0200
> Vadim Kochan <vadim4j@gmail.com> wrote:
>
> > May be it would be good to start with generic script which generates
> > br2_fragment by specifying the path to the toolchain ?
>
> 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.
The existing script which validates the toolchain (during the build
before the installation into the host part) uses some set of checks -
rpc, wchar, threads supporting.
So, it would be good to use such approach for the toolchain fragment
generation. Or such script already exist ?
> Best regards,
>
> Thomas
Regards,
Vadim Kochan
next prev parent reply other threads:[~2019-12-03 11:06 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 [this message]
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
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='CAMw6YJL=DREwg6HM-xnijK=nhxJGaf4P_Jga+46W2jGBMqmE3g@mail.gmail.com' \
--to=vadim4j@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.