From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross@burtonini.com>, Khem Raj <raj.khem@gmail.com>
Cc: Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] lttng-tools: Do not build for riscv64
Date: Thu, 27 Aug 2020 09:43:13 +0100 [thread overview]
Message-ID: <0d4bd302ffe98c7418087822538b689484c1774b.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAAnfSTuhGz+wyguPojV_0YYE7VzPS4BZcBqXFu-=FjQAU2emmg@mail.gmail.com>
On Thu, 2020-08-27 at 09:21 +0100, Ross Burton wrote:
> On Thu, 27 Aug 2020 at 03:17, Khem Raj <raj.khem@gmail.com> wrote:
> > > LTTng does not have a hard requirement on lttng-modules (on
> > > paper), when kernel modules
> > > (tracer) is not present kernel tracing is disabled and only
> > > userspace tracing is
> > > available.
> > >
> > > Was there any report that lttng-ust (userspace tracing) is not
> > > working as
> > > intended on riscv64?
> >
> > No, but lttng-tools have this as rdep for ptest packages which is
> > not
> > controlled via packageconfig or something.
>
> Make it a recommends instead?
Those are still fatal from a build providers perspective...
Sounds to me like we should move the conditional skipping in lttng-
modules somewhere lttng-tools can also see it, then use that in the
RDEPENDS_lttng-tools-ptest...
Cheers,
Richard
prev parent reply other threads:[~2020-08-27 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 5:41 [PATCH] lttng-tools: Do not build for riscv64 Khem Raj
2020-08-26 14:00 ` [OE-core] " Jonathan Rajotte-Julien
2020-08-27 2:16 ` Khem Raj
2020-08-27 8:21 ` Ross Burton
2020-08-27 8:43 ` Richard Purdie [this message]
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=0d4bd302ffe98c7418087822538b689484c1774b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jonathan.rajotte-julien@efficios.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross@burtonini.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox