All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
	Loic Poulain <loic.poulain@linaro.org>,
	openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH v1 3/4] BCC: Add build recipe
Date: Wed, 19 Feb 2020 17:44:52 +0800	[thread overview]
Message-ID: <20200219094452.GA11073@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20200218072726.GB9945@leoy-ThinkPad-X240s>

Hi Khem,

On Tue, Feb 18, 2020 at 03:27:26PM +0800, Leo Yan wrote:
> Hi Khem,
> 
> On Mon, Feb 17, 2020 at 10:30:46PM -0800, Khem Raj wrote:
> 
> [...]
> 
> > > +DEPENDS += "bison-native \
> > > +            ninja-native \
> > > +            elfutils-native \
> > > +            flex-native \
> > > +            ${MLPREFIX}elfutils \
> > > +            ${MLPREFIX}binutils \
> > > +            ${MLPREFIX}flex \
> > > +            luajit \
> > > +            clang \
> > > +            "
> > > +
> > 
> > this will add meta-clang dependency directly into meta-oe, which is not desired
> > is it possible to make it optional or perhaps marked when meta-clang
> > is not in BBLAYERS
> 
> Thanks a lot for reviewing.  clang is mandotory for BCC to compile
> eBPF programs, so I think we cannot build clang as optional for BCC.
> 
> For marking the recipe when meta-clang is not in BBLAYERS, I searched
> with google but seems 'LAYERDEPENDS' and 'BBMASK' both are not suitable
> for this case.  Could you give more detailed info for how to do this?

Just want to ask a following question.

Since BCC and bpftrace both are heavily relying on LLVM/Clang for their
tracing, do you think it's a good idea to merge BCC and bpftrace into
meta-clang layer, e.g. place into /meta-clang/recipes-devtools/?
If so, we can easily resolve the dependency issue and avoid to introduce
mess between meta-oe and meta-clang.

For the tool ply, it's simple and doesn't depend on Clang.  So should
keep it into meta-oe/recipes-devtools/ folder?  Also welcome any
suggestion for this.

Thanks,
Leo Yan


  reply	other threads:[~2020-02-19  9:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18  5:25 [meta-oe][PATCH v1 0/4] eBPF tools: Add recipes Leo Yan
2020-02-18  5:25 ` [meta-oe][PATCH v1 1/4] Ply: Add recipe for git version Leo Yan
2020-02-20 15:41   ` Khem Raj
2020-02-21  9:03     ` Leo Yan
2020-02-18  5:25 ` [meta-oe][PATCH v1 2/4] luajit: Add luajit 2.1.0-beta3 recipe Leo Yan
2020-02-19 23:07   ` Khem Raj
2020-02-18  5:25 ` [meta-oe][PATCH v1 3/4] BCC: Add build recipe Leo Yan
2020-02-18  6:30   ` Khem Raj
2020-02-18  7:27     ` Leo Yan
2020-02-19  9:44       ` Leo Yan [this message]
2020-02-19 17:16         ` Khem Raj
2020-02-18  5:25 ` [meta-oe][PATCH v1 4/4] bpftrace: " Leo Yan

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=20200219094452.GA11073@leoy-ThinkPad-X240s \
    --to=leo.yan@linaro.org \
    --cc=daniel.thompson@linaro.org \
    --cc=loic.poulain@linaro.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.