buildtools-extended-tarball wrapping builds

buildtools-extended-tarball wrapping builds

[Richard Purdie]

Hi,

I just wanted to mention that we now have the ability to wrap builds on
specific workers with specific buildtools tarballs.

Currently this functionality is in master, we do have the option of
porting the helper code to other stable branches.

We have had multiple issues, with the infrastucture internal url/cert
handling, git/cert environment issues, an issue with eSDK testing (next
has a fix in testing), the crypt fix already submitted (meaning M2's
tarball doesn't help)  and so on, I'm hoping we've gotten to the bottom
of those.

This does mean we could drop gcc 4.8/4.9 support if we wanted to and
rely on the tarball support for centos7/debian8. I'm torn on that, we
are still missing:

a) Support for wrapping a build with buildtools more auotmatically
(like we do with uninative)

b) documentation of buildtools-extended-tarball

and to drop, we'd probably need these pieces.

I'd note the people who vocally said they needed centos7 support are
not the ones who are doing this work. The only reason I'm pushing it is
I know it will ultimately help support our LTS efforts.

Cheers,

Richard

Re: [Openembedded-architecture] buildtools-extended-tarball wrapping builds

[Adrian Bunk]

On Sat, Mar 07, 2020 at 04:17:28PM +0000, Richard Purdie wrote:
>...
> This does mean we could drop gcc 4.8/4.9 support if we wanted to and
> rely on the tarball support for centos7/debian8.
>...

Debian 8
- will have LTS support ending at the end of June, and
- ships Python 3.4, which is no longer supported by bitbake.

3 months ago Yocto master stopped working on Debian 8,
and as expected noone complained.

> Cheers,
> 
> Richard

cu
Adrian

Re: [Openembedded-architecture] buildtools-extended-tarball wrapping builds

[Richard Purdie]

On Mon, 2020-03-09 at 12:52 +0200, Adrian Bunk wrote:
> On Sat, Mar 07, 2020 at 04:17:28PM +0000, Richard Purdie wrote:
> > ...
> > This does mean we could drop gcc 4.8/4.9 support if we wanted to
> > and
> > rely on the tarball support for centos7/debian8.
> > ...
> 
> Debian 8
> - will have LTS support ending at the end of June, and
> - ships Python 3.4, which is no longer supported by bitbake.
> 
> 3 months ago Yocto master stopped working on Debian 8,
> and as expected noone complained.

We still have one debian8 autobuilder worker:

https://autobuilder.yoctoproject.org/typhoon/#/workers/9

and with buildtools tarball it works 'fine'.

Cheers,

Richard

Re: [Openembedded-architecture] buildtools-extended-tarball wrapping builds

[Adrian Bunk]

On Mon, Mar 09, 2020 at 11:41:13AM +0000, Richard Purdie wrote:
> On Mon, 2020-03-09 at 12:52 +0200, Adrian Bunk wrote:
> > On Sat, Mar 07, 2020 at 04:17:28PM +0000, Richard Purdie wrote:
> > > ...
> > > This does mean we could drop gcc 4.8/4.9 support if we wanted to
> > > and
> > > rely on the tarball support for centos7/debian8.
> > > ...
> > 
> > Debian 8
> > - will have LTS support ending at the end of June, and
> > - ships Python 3.4, which is no longer supported by bitbake.
> > 
> > 3 months ago Yocto master stopped working on Debian 8,
> > and as expected noone complained.
> 
> We still have one debian8 autobuilder worker:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/workers/9
> 
> and with buildtools tarball it works 'fine'.

Ah right, buildtools tarball ships python3.
So yes, this invalidates my second point.

> Cheers,
> 
> Richard

cu
Adrian

Re: [Openembedded-architecture] buildtools-extended-tarball wrapping builds

[Rich Persaud]

[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]

On Mar 7, 2020, at 11:17, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> Hi,
> 
> I just wanted to mention that we now have the ability to wrap builds on
> specific workers with specific buildtools tarballs.
> 
> Currently this functionality is in master, we do have the option of
> porting the helper code to other stable branches.
> 
> We have had multiple issues, with the infrastucture internal url/cert
> handling, git/cert environment issues, an issue with eSDK testing (next
> has a fix in testing), the crypt fix already submitted (meaning M2's
> tarball doesn't help)  and so on, I'm hoping we've gotten to the bottom
> of those.
> 
> This does mean we could drop gcc 4.8/4.9 support if we wanted to and
> rely on the tarball support for centos7/debian8. I'm torn on that, we
> are still missing:
> 
> a) Support for wrapping a build with buildtools more auotmatically
> (like we do with uninative)
> 
> b) documentation of buildtools-extended-tarball

This would be valuable to wrap older Haskell [1] and Ocaml [2] compilers, which are often challenging to support with newer versions of OE.  I've tested buildtools-extended-tarball with an OpenXT build, but we would need to use an older tarball for the Haskell/Ocaml native compilers.

Rich

[1] https://github.com/OpenXT/meta-openxt-haskell-platform
[2] https://github.com/OpenXT/meta-openxt-ocaml-platform


[-- Attachment #2: Type: text/html, Size: 2200 bytes --]