* Compilers from.. debian?
@ 2018-08-14 19:21 Matt Hart
2018-08-15 15:21 ` [kernelci] " Kevin Hilman
0 siblings, 1 reply; 6+ messages in thread
From: Matt Hart @ 2018-08-14 19:21 UTC (permalink / raw)
To: kernelci
Hi all,
Does anyone have a strong opinion about where we get our compiler releases from?
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.
Thanks!
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [kernelci] Compilers from.. debian?
2018-08-14 19:21 Compilers from.. debian? Matt Hart
@ 2018-08-15 15:21 ` Kevin Hilman
2018-08-15 15:39 ` broonie
0 siblings, 1 reply; 6+ messages in thread
From: Kevin Hilman @ 2018-08-15 15:21 UTC (permalink / raw)
To: Matt Hart; +Cc: kernelci
"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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [kernelci] Compilers from.. debian?
2018-08-15 15:21 ` [kernelci] " Kevin Hilman
@ 2018-08-15 15:39 ` broonie
2018-08-15 16:05 ` Matt Hart
0 siblings, 1 reply; 6+ messages in thread
From: broonie @ 2018-08-15 15:39 UTC (permalink / raw)
To: kernelci; +Cc: Matt Hart
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
On Wed, 15 Aug 2018, 4:21 pm Kevin Hilman, <khilman@baylibre.com> wrote:
> "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!
>
The only concern I can think of is that it's going to be a bit harder for
those not fortunate enough to run Debian to get the toolchains if there's
some reason to reproduce things. On the other hand that's a rare occurrence
and with moving the builders more to Docker there's always the option of
using the container to get the compilers on other OSs.
> Kevin
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2084 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [kernelci] Compilers from.. debian?
2018-08-15 15:39 ` broonie
@ 2018-08-15 16:05 ` Matt Hart
2018-08-15 16:27 ` Mark Brown
0 siblings, 1 reply; 6+ messages in thread
From: Matt Hart @ 2018-08-15 16:05 UTC (permalink / raw)
To: Mark Brown; +Cc: kernelci
On 15 August 2018 at 16:39, Mark Brown <broonie@kernel.org> wrote:
>
>
> On Wed, 15 Aug 2018, 4:21 pm Kevin Hilman, <khilman@baylibre.com> wrote:
>>
>> "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!
>
>
> The only concern I can think of is that it's going to be a bit harder for
> those not fortunate enough to run Debian to get the toolchains if there's
> some reason to reproduce things. On the other hand that's a rare occurrence
> and with moving the builders more to Docker there's always the option of
> using the container to get the compilers on other OSs.
I've been thinking about adding a section to the build page of "repeat
this build" and a link to either a dockerfile or image which runs the
identical steps in the same environment, it could be a really nice
feature to add.
>
>>
>> Kevin
>>
>>
>>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [kernelci] Compilers from.. debian?
2018-08-15 16:05 ` Matt Hart
@ 2018-08-15 16:27 ` Mark Brown
2018-08-20 13:36 ` Ana Guerrero Lopez
0 siblings, 1 reply; 6+ messages in thread
From: Mark Brown @ 2018-08-15 16:27 UTC (permalink / raw)
To: kernelci
[-- Attachment #1: Type: text/plain, Size: 1977 bytes --]
On Wed, 15 Aug 2018, 5:05 pm Matt Hart, <matthew.hart@linaro.org> wrote:
> On 15 August 2018 at 16:39, Mark Brown <broonie@kernel.org> wrote:
> >
> >
> > On Wed, 15 Aug 2018, 4:21 pm Kevin Hilman, <khilman@baylibre.com> wrote:
> >>
> >> "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!
> >
> >
> > The only concern I can think of is that it's going to be a bit harder for
> > those not fortunate enough to run Debian to get the toolchains if there's
> > some reason to reproduce things. On the other hand that's a rare
> occurrence
> > and with moving the builders more to Docker there's always the option of
> > using the container to get the compilers on other OSs.
>
> I've been thinking about adding a section to the build page of "repeat
> this build" and a link to either a dockerfile or image which runs the
> identical steps in the same environment, it could be a really nice
> feature to add.
>
That'd be a neat thing to have!
> >
> >>
> >> Kevin
> >>
> >>
> >>
> >
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3060 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [kernelci] Compilers from.. debian?
2018-08-15 16:27 ` Mark Brown
@ 2018-08-20 13:36 ` Ana Guerrero Lopez
0 siblings, 0 replies; 6+ messages in thread
From: Ana Guerrero Lopez @ 2018-08-20 13:36 UTC (permalink / raw)
To: kernelci
[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]
On 15/08/18 18:27, Mark Brown wrote:
>
>
> On Wed, 15 Aug 2018, 5:05 pm Matt Hart, <matthew.hart@linaro.org
> <mailto:matthew.hart@linaro.org>> wrote:
>
> On 15 August 2018 at 16:39, Mark Brown <broonie@kernel.org
> <mailto:broonie@kernel.org>> wrote:
> >
> >
> > On Wed, 15 Aug 2018, 4:21 pm Kevin Hilman, <khilman@baylibre.com
> <mailto:khilman@baylibre.com>> wrote:
> >>
> >> "Matt Hart" <matthew.hart@linaro.org
> <mailto: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!
> >
> >
> > The only concern I can think of is that it's going to be a bit
> harder for
> > those not fortunate enough to run Debian to get the toolchains
> if there's
> > some reason to reproduce things. On the other hand that's a rare
> occurrence
> > and with moving the builders more to Docker there's always the
> option of
> > using the container to get the compilers on other OSs.
>
> I've been thinking about adding a section to the build page of "repeat
> this build" and a link to either a dockerfile or image which runs the
> identical steps in the same environment, it could be a really nice
> feature to add.
>
>
> That'd be a neat thing to have!
>
+1 and thank you for taking care of this.
Ana
[-- Attachment #2: Type: text/html, Size: 4099 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-08-20 13:36 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-08-14 19:21 Compilers from.. debian? Matt Hart
2018-08-15 15:21 ` [kernelci] " Kevin Hilman
2018-08-15 15:39 ` broonie
2018-08-15 16:05 ` Matt Hart
2018-08-15 16:27 ` Mark Brown
2018-08-20 13:36 ` Ana Guerrero Lopez
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox