From: "Kevin Hilman" <khilman@baylibre.com>
To: Matt Hart <matthew.hart@linaro.org>
Cc: kernelci@groups.io
Subject: Re: [kernelci] Compilers from.. debian?
Date: Wed, 15 Aug 2018 08:21:49 -0700 [thread overview]
Message-ID: <7hefezlkoi.fsf@baylibre.com> (raw)
In-Reply-To: <CAH+k93God7SdCeet-S=n4iUmLvyJr4+hORa=W852N_tKWFo8Qw@mail.gmail.com> (Matt Hart's message of "Tue, 14 Aug 2018 20:21:09 +0100")
"Matt Hart" <matthew.hart@linaro.org> writes:
> Does anyone have a strong opinion about where we get our compiler releases from?
I think the current tarball way is a hack and not scalable, so...
> Currently it's a mash up of Linaro for ARM(32/64), MIPS from unknown,
> and X86 from whatever ubuntu is installed on the builder
>
> As part of my work to start building with multiple compiler versions,
> I've been creating Dockerfiles for the builders with different
> compiler versions installed in them. As I've been doing this, it's
> been really easy to just install the various compilers packages from
> Debian. They also cover a lot of architectures we're hoping to add in
> the future.
>
> Anyone mind if we start using Debian toolchain releases in future?
> I'm no toolchain expert, so I'm looking for some opinions.
It's better than what we're doing today, and has a much clearer
upgrade/migration path, so I say go for it!
Kevin
next prev parent reply other threads:[~2018-08-15 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 19:21 Compilers from.. debian? Matt Hart
2018-08-15 15:21 ` Kevin Hilman [this message]
2018-08-15 15:39 ` [kernelci] " broonie
2018-08-15 16:05 ` Matt Hart
2018-08-15 16:27 ` Mark Brown
2018-08-20 13:36 ` Ana Guerrero Lopez
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=7hefezlkoi.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=kernelci@groups.io \
--cc=matthew.hart@linaro.org \
/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