All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jon Mason" <jdmason@kudzu.us>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: Ross Burton <ross@burtonini.com>, meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH 1/3] arm-toolchain/external-arm-toolchain: inhibit build dependencies
Date: Thu, 13 May 2021 10:58:31 -0400	[thread overview]
Message-ID: <20210513145831.GA11769@kudzu.us> (raw)
In-Reply-To: <CAFA6WYOd_hGzeP+CAvqb5Oih8aG1k4uLAeZTu8KC6OSUvXGy5w@mail.gmail.com>

On Tue, May 11, 2021 at 10:05:58AM +0530, Sumit Garg wrote:
> On Mon, 10 May 2021 at 23:46, Ross Burton <ross@burtonini.com> wrote:
> >
> > These recipes don't build anything, so there's no need to depend on a
> > toolchain.
> >
> > Change-Id: I49b641fb54839c30255a11a7c9d5798c8e4afd2a
> > Signed-off-by: Ross Burton <ross.burton@arm.com>
> > ---
> >  .../external-arm-toolchain/arm-binary-toolchain.inc             | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> 
> For the series:
> 
> Acked-by: Sumit Garg <sumit.garg@linaro.org>

Apologies, I was too quick with the trigger and pulled these in before
you acked.  In my defense, it did pass our internal build CI, and my
WIP testing. We're still working on a way to have it public, but here
is a preview of just the building:
https://gitlab.com/jonmason00/meta-arm/-/pipelines/298844578

You can see from the names that we are getting some coverage for
clang, Arm Binary toolchains, Arm GCC sources, and musl (for good
measure).  Not enough computing power currently for every possible
permutation, but if you can see any obvious coverage gaps, let me/us
know.

Thanks,
Jon

> 
> -Sumit
> 
> > diff --git a/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/arm-binary-toolchain.inc b/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/arm-binary-toolchain.inc
> > index 2fbabfb..046ab62 100644
> > --- a/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/arm-binary-toolchain.inc
> > +++ b/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/arm-binary-toolchain.inc
> > @@ -1,3 +1,5 @@
> > +INHIBIT_DEFAULT_DEPS = "1"
> > +
> >  FILES_${PN} = "${datadir} ${bindir}"
> >
> >  BINNAME = "${@d.getVar("BPN").strip("gcc-")}"
> > --
> > 2.25.1
> >
> >
> > 
> >

> 
> 
> 


  reply	other threads:[~2021-05-13 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 18:16 [PATCH 1/3] arm-toolchain/external-arm-toolchain: inhibit build dependencies Ross Burton
2021-05-10 18:16 ` [PATCH 2/3] arm-toolchain/armcompiler: add upstream release checking Ross Burton
2021-05-10 18:16 ` [PATCH 3/3] arm-toolchain/armcompiler: remove pointless PROVIDES Ross Burton
2021-05-11  4:35 ` [meta-arm] [PATCH 1/3] arm-toolchain/external-arm-toolchain: inhibit build dependencies Sumit Garg
2021-05-13 14:58   ` Jon Mason [this message]
2021-05-13 15:20     ` Denys Dmytriyenko
2021-05-14  5:04     ` Sumit Garg

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=20210513145831.GA11769@kudzu.us \
    --to=jdmason@kudzu.us \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=ross@burtonini.com \
    --cc=sumit.garg@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 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.