Proposal to import ARM GCC toolchain recipes into meta-arm

Proposal to import ARM GCC toolchain recipes into meta-arm

[Sumit Garg]

Hi Jon and all,

As you may be aware that Linaro used to maintain meta-linaro-toolchain
layer [1] in meta-linaro tree for GCC tool-set releases from Linaro
till GCC 7.

And since GCC 8, the tool-set release and maintenance work was
transferred to ARM. But meta-linaro-toolchain layer continued support
for ARM GCC tool-set releases as well.

In future, I think meta-arm tree [2] shall be an appropriate place to
host ARM GCC toolchain recipes as an additional meta-arm-toolchain
layer. Also, with the latest integration [3] for ARM GCC 9.2 toolchain
in meta-linaro, recipes are well tested and seems to be stable. So I
would like to propose import of ARM GCC toolchain recipes into
meta-arm.

I am looking forward to any comments or suggestions regarding this proposal.

[1] https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro-toolchain
[2] https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/
[3] https://lists.yoctoproject.org/g/yocto/message/48094

Regards,
Sumit

Re: Proposal to import ARM GCC toolchain recipes into meta-arm

[Denys Dmytriyenko]

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

As one of the original developers of the whole "external-toolchain" support[1] and still being an active contributor[2], spanning through CodeSourcery->Linaro->Arm recipes, I would certainly welcome this move!

BTW, what is the branching strategy for this layer - will there be release branches, like thud, zeus, etc.?

[1] https://git.openembedded.org/openembedded/log/recipes/meta/external-toolchain-csl.bb
[2] https://git.linaro.org/openembedded/meta-linaro.git/log/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb

--
Denys

On Thu, Jan 23, 2020 at 02:39 AM, Sumit Garg wrote:

> 
> Hi Jon and all,
> 
> As you may be aware that Linaro used to maintain meta-linaro-toolchain
> layer [1] in meta-linaro tree for GCC tool-set releases from Linaro
> till GCC 7.
> 
> And since GCC 8, the tool-set release and maintenance work was
> transferred to ARM. But meta-linaro-toolchain layer continued support
> for ARM GCC tool-set releases as well.
> 
> In future, I think meta-arm tree [2] shall be an appropriate place to
> host ARM GCC toolchain recipes as an additional meta-arm-toolchain
> layer. Also, with the latest integration [3] for ARM GCC 9.2 toolchain
> in meta-linaro, recipes are well tested and seems to be stable. So I
> would like to propose import of ARM GCC toolchain recipes into
> meta-arm.
> 
> I am looking forward to any comments or suggestions regarding this
> proposal.
> 
> [1] https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro-toolchain
> 
> [2] https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/
> [3] https://lists.yoctoproject.org/g/yocto/message/48094
> 
> Regards,
> Sumit

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

Re: [meta-arm] Proposal to import ARM GCC toolchain recipes into meta-arm

[Sumit Garg]

On Fri, 24 Jan 2020 at 06:21, Denys Dmytriyenko <denis@denix.org> wrote:
>
> As one of the original developers of the whole "external-toolchain" support[1] and still being an active contributor[2], spanning through CodeSourcery->Linaro->Arm recipes, I would certainly welcome this move!

Thanks Denys for your contribution.

>
> BTW, what is the branching strategy for this layer - will there be release branches, like thud, zeus, etc.?

I would expect meta-arm tree to also support thud, warrior and zeus
branches since external-arm-toolchain support all these OE release
branches.

-Sumit

>
> [1] https://git.openembedded.org/openembedded/log/recipes/meta/external-toolchain-csl.bb
> [2] https://git.linaro.org/openembedded/meta-linaro.git/log/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb
>
> --
> Denys
>
>
> On Thu, Jan 23, 2020 at 02:39 AM, Sumit Garg wrote:
>
> Hi Jon and all,
>
> As you may be aware that Linaro used to maintain meta-linaro-toolchain
> layer [1] in meta-linaro tree for GCC tool-set releases from Linaro
> till GCC 7.
>
> And since GCC 8, the tool-set release and maintenance work was
> transferred to ARM. But meta-linaro-toolchain layer continued support
> for ARM GCC tool-set releases as well.
>
> In future, I think meta-arm tree [2] shall be an appropriate place to
> host ARM GCC toolchain recipes as an additional meta-arm-toolchain
> layer. Also, with the latest integration [3] for ARM GCC 9.2 toolchain
> in meta-linaro, recipes are well tested and seems to be stable. So I
> would like to propose import of ARM GCC toolchain recipes into
> meta-arm.
>
> I am looking forward to any comments or suggestions regarding this proposal.
>
> [1] https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro-toolchain
> [2] https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/
> [3] https://lists.yoctoproject.org/g/yocto/message/48094
>
> Regards,
> Sumit
>
> 

Re: [meta-arm] Proposal to import ARM GCC toolchain recipes into meta-arm

[Jon Mason]

On Thu, Jan 23, 2020 at 5:39 AM Sumit Garg <sumit.garg@linaro.org> wrote:
>
> Hi Jon and all,
>
> As you may be aware that Linaro used to maintain meta-linaro-toolchain
> layer [1] in meta-linaro tree for GCC tool-set releases from Linaro
> till GCC 7.
>
> And since GCC 8, the tool-set release and maintenance work was
> transferred to ARM. But meta-linaro-toolchain layer continued support
> for ARM GCC tool-set releases as well.
>
> In future, I think meta-arm tree [2] shall be an appropriate place to
> host ARM GCC toolchain recipes as an additional meta-arm-toolchain
> layer. Also, with the latest integration [3] for ARM GCC 9.2 toolchain
> in meta-linaro, recipes are well tested and seems to be stable. So I
> would like to propose import of ARM GCC toolchain recipes into
> meta-arm.
>
> I am looking forward to any comments or suggestions regarding this proposal.

I am very much in favor of this and was working on a recipe to do this
before the end of last year (but was not working and was not able to
get back to it yet).  If you send emails to this mailing list with the
relevant code, I'll happily pull them in.  Since this is already in
the meta-linaro tree, I think the optics of you submitting it to
meta-arm are better.  However, if you are busy with other things, I
can pull all of the relevant recipes in from meta-linaro.  Just tell
me which you prefer.

Thanks,
Jon

> [1] https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro-toolchain
> [2] https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/
> [3] https://lists.yoctoproject.org/g/yocto/message/48094
>
> Regards,
> Sumit
> 

Re: [meta-arm] Proposal to import ARM GCC toolchain recipes into meta-arm

[Jon Mason]

On Fri, Jan 24, 2020 at 12:18 AM Sumit Garg <sumit.garg@linaro.org> wrote:
>
> On Fri, 24 Jan 2020 at 06:21, Denys Dmytriyenko <denis@denix.org> wrote:
> >
> > As one of the original developers of the whole "external-toolchain" support[1] and still being an active contributor[2], spanning through CodeSourcery->Linaro->Arm recipes, I would certainly welcome this move!
>
> Thanks Denys for your contribution.
>
> >
> > BTW, what is the branching strategy for this layer - will there be release branches, like thud, zeus, etc.?
>
> I would expect meta-arm tree to also support thud, warrior and zeus
> branches since external-arm-toolchain support all these OE release
> branches.

Our plan was only to support zeus and releases going forward.  This
was to limit the releases we need to test on.  If there is a desire
for more, then we can accommodate.

And to answer Denys' original question, yes we will create branches
for each one.  Given that we are currently only supporting zeus, this
is why we only have master now.  If there is a request for me (per
above), then we will branch as needed.

Thanks,
Jon


>
> -Sumit
>
> >
> > [1] https://git.openembedded.org/openembedded/log/recipes/meta/external-toolchain-csl.bb
> > [2] https://git.linaro.org/openembedded/meta-linaro.git/log/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb
> >
> > --
> > Denys
> >
> >
> > On Thu, Jan 23, 2020 at 02:39 AM, Sumit Garg wrote:
> >
> > Hi Jon and all,
> >
> > As you may be aware that Linaro used to maintain meta-linaro-toolchain
> > layer [1] in meta-linaro tree for GCC tool-set releases from Linaro
> > till GCC 7.
> >
> > And since GCC 8, the tool-set release and maintenance work was
> > transferred to ARM. But meta-linaro-toolchain layer continued support
> > for ARM GCC tool-set releases as well.
> >
> > In future, I think meta-arm tree [2] shall be an appropriate place to
> > host ARM GCC toolchain recipes as an additional meta-arm-toolchain
> > layer. Also, with the latest integration [3] for ARM GCC 9.2 toolchain
> > in meta-linaro, recipes are well tested and seems to be stable. So I
> > would like to propose import of ARM GCC toolchain recipes into
> > meta-arm.
> >
> > I am looking forward to any comments or suggestions regarding this proposal.
> >
> > [1] https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro-toolchain
> > [2] https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/
> > [3] https://lists.yoctoproject.org/g/yocto/message/48094
> >
> > Regards,
> > Sumit
> >
> >
> 

Re: [meta-arm] Proposal to import ARM GCC toolchain recipes into meta-arm

[Sumit Garg]

On Sat, 25 Jan 2020 at 02:35, Jon Mason <jdmason@kudzu.us> wrote:
>
> On Thu, Jan 23, 2020 at 5:39 AM Sumit Garg <sumit.garg@linaro.org> wrote:
> >
> > Hi Jon and all,
> >
> > As you may be aware that Linaro used to maintain meta-linaro-toolchain
> > layer [1] in meta-linaro tree for GCC tool-set releases from Linaro
> > till GCC 7.
> >
> > And since GCC 8, the tool-set release and maintenance work was
> > transferred to ARM. But meta-linaro-toolchain layer continued support
> > for ARM GCC tool-set releases as well.
> >
> > In future, I think meta-arm tree [2] shall be an appropriate place to
> > host ARM GCC toolchain recipes as an additional meta-arm-toolchain
> > layer. Also, with the latest integration [3] for ARM GCC 9.2 toolchain
> > in meta-linaro, recipes are well tested and seems to be stable. So I
> > would like to propose import of ARM GCC toolchain recipes into
> > meta-arm.
> >
> > I am looking forward to any comments or suggestions regarding this proposal.
>
> I am very much in favor of this and was working on a recipe to do this
> before the end of last year (but was not working and was not able to
> get back to it yet).  If you send emails to this mailing list with the
> relevant code, I'll happily pull them in.  Since this is already in
> the meta-linaro tree, I think the optics of you submitting it to
> meta-arm are better.  However, if you are busy with other things, I
> can pull all of the relevant recipes in from meta-linaro.  Just tell
> me which you prefer.

I have posted a patch [1] to this list in order to import ARM GNU-A
toolset recipes as new meta-arm-toolchain. Please have a look.

[1] https://lists.yoctoproject.org/g/meta-arm/topic/70151367

-Sumit

>
> Thanks,
> Jon
>
> > [1] https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro-toolchain
> > [2] https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/
> > [3] https://lists.yoctoproject.org/g/yocto/message/48094
> >
> > Regards,
> > Sumit
> >
> 

Re: [meta-arm] Proposal to import ARM GCC toolchain recipes into meta-arm

[Denys Dmytriyenko]

On Fri, Jan 24, 2020 at 04:12:39PM -0500, Jon Mason wrote:
> On Fri, Jan 24, 2020 at 12:18 AM Sumit Garg <sumit.garg@linaro.org> wrote:
> >
> > On Fri, 24 Jan 2020 at 06:21, Denys Dmytriyenko <denis@denix.org> wrote:
> > >
> > > As one of the original developers of the whole "external-toolchain" support[1] and still being an active contributor[2], spanning through CodeSourcery->Linaro->Arm recipes, I would certainly welcome this move!
> >
> > Thanks Denys for your contribution.
> >
> > >
> > > BTW, what is the branching strategy for this layer - will there be release branches, like thud, zeus, etc.?
> >
> > I would expect meta-arm tree to also support thud, warrior and zeus
> > branches since external-arm-toolchain support all these OE release
> > branches.
> 
> Our plan was only to support zeus and releases going forward.  This
> was to limit the releases we need to test on.  If there is a desire
> for more, then we can accommodate.
> 
> And to answer Denys' original question, yes we will create branches
> for each one.  Given that we are currently only supporting zeus, this
> is why we only have master now.  If there is a request for me (per
> above), then we will branch as needed.

Jon,

Thank you for the details. One more question - do Arm-originated patches go 
through the same public list or are they reviewed internally before merging? 
Thanks!

-- 
Denys


> > > [1] https://git.openembedded.org/openembedded/log/recipes/meta/external-toolchain-csl.bb
> > > [2] https://git.linaro.org/openembedded/meta-linaro.git/log/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb
> > >
> > > --
> > > Denys
> > >
> > >
> > > On Thu, Jan 23, 2020 at 02:39 AM, Sumit Garg wrote:
> > >
> > > Hi Jon and all,
> > >
> > > As you may be aware that Linaro used to maintain meta-linaro-toolchain
> > > layer [1] in meta-linaro tree for GCC tool-set releases from Linaro
> > > till GCC 7.
> > >
> > > And since GCC 8, the tool-set release and maintenance work was
> > > transferred to ARM. But meta-linaro-toolchain layer continued support
> > > for ARM GCC tool-set releases as well.
> > >
> > > In future, I think meta-arm tree [2] shall be an appropriate place to
> > > host ARM GCC toolchain recipes as an additional meta-arm-toolchain
> > > layer. Also, with the latest integration [3] for ARM GCC 9.2 toolchain
> > > in meta-linaro, recipes are well tested and seems to be stable. So I
> > > would like to propose import of ARM GCC toolchain recipes into
> > > meta-arm.
> > >
> > > I am looking forward to any comments or suggestions regarding this proposal.
> > >
> > > [1] https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro-toolchain
> > > [2] https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/
> > > [3] https://lists.yoctoproject.org/g/yocto/message/48094
> > >
> > > Regards,
> > > Sumit
> > >
> > >
> > 

> 

Re: [meta-arm] Proposal to import ARM GCC toolchain recipes into meta-arm

[Jon Mason]

On Mon, Jan 27, 2020 at 7:47 PM Denys Dmytriyenko <denis@denix.org> wrote:
>
> On Fri, Jan 24, 2020 at 04:12:39PM -0500, Jon Mason wrote:
> > On Fri, Jan 24, 2020 at 12:18 AM Sumit Garg <sumit.garg@linaro.org> wrote:
> > >
> > > On Fri, 24 Jan 2020 at 06:21, Denys Dmytriyenko <denis@denix.org> wrote:
> > > >
> > > > As one of the original developers of the whole "external-toolchain" support[1] and still being an active contributor[2], spanning through CodeSourcery->Linaro->Arm recipes, I would certainly welcome this move!
> > >
> > > Thanks Denys for your contribution.
> > >
> > > >
> > > > BTW, what is the branching strategy for this layer - will there be release branches, like thud, zeus, etc.?
> > >
> > > I would expect meta-arm tree to also support thud, warrior and zeus
> > > branches since external-arm-toolchain support all these OE release
> > > branches.
> >
> > Our plan was only to support zeus and releases going forward.  This
> > was to limit the releases we need to test on.  If there is a desire
> > for more, then we can accommodate.
> >
> > And to answer Denys' original question, yes we will create branches
> > for each one.  Given that we are currently only supporting zeus, this
> > is why we only have master now.  If there is a request for me (per
> > above), then we will branch as needed.
>
> Jon,
>
> Thank you for the details. One more question - do Arm-originated patches go
> through the same public list or are they reviewed internally before merging?
> Thanks!


The internal process should be that the patch is reviewed internally
via gerrit, then pushed externally to meta-arm mailing list for
review, then pushed to the external git repo (assuming no problems
found at each step).  Since the git tree was not public until
recently, I've been lax about enforcing this.  However, I will make
sure that this is enforced going forward.

Thanks,
Jon


>
> --
> Denys
>
>
> > > > [1] https://git.openembedded.org/openembedded/log/recipes/meta/external-toolchain-csl.bb
> > > > [2] https://git.linaro.org/openembedded/meta-linaro.git/log/meta-linaro-toolchain/recipes-devtools/external-arm-toolchain/external-arm-toolchain.bb
> > > >
> > > > --
> > > > Denys
> > > >
> > > >
> > > > On Thu, Jan 23, 2020 at 02:39 AM, Sumit Garg wrote:
> > > >
> > > > Hi Jon and all,
> > > >
> > > > As you may be aware that Linaro used to maintain meta-linaro-toolchain
> > > > layer [1] in meta-linaro tree for GCC tool-set releases from Linaro
> > > > till GCC 7.
> > > >
> > > > And since GCC 8, the tool-set release and maintenance work was
> > > > transferred to ARM. But meta-linaro-toolchain layer continued support
> > > > for ARM GCC tool-set releases as well.
> > > >
> > > > In future, I think meta-arm tree [2] shall be an appropriate place to
> > > > host ARM GCC toolchain recipes as an additional meta-arm-toolchain
> > > > layer. Also, with the latest integration [3] for ARM GCC 9.2 toolchain
> > > > in meta-linaro, recipes are well tested and seems to be stable. So I
> > > > would like to propose import of ARM GCC toolchain recipes into
> > > > meta-arm.
> > > >
> > > > I am looking forward to any comments or suggestions regarding this proposal.
> > > >
> > > > [1] https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro-toolchain
> > > > [2] https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/
> > > > [3] https://lists.yoctoproject.org/g/yocto/message/48094
> > > >
> > > > Regards,
> > > > Sumit
> > > >
> > > >
> > >
>
> >
>
>