All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrey Zhizhikin" <andrey.z@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/4] lttng-modules: update to 2.13.0
Date: Fri, 20 Aug 2021 13:13:14 +0200	[thread overview]
Message-ID: <CAHtQpK4rAfAjB7dwXoz4D42887whGu5xgrxGcCxKRYmNUiE3-Q@mail.gmail.com> (raw)
In-Reply-To: <91f494738fb9c63499fae982fb7b09cb29c3afed.1629213685.git.bruce.ashfield@gmail.com>

Hello Bruce,

On Tue, Aug 17, 2021 at 5:27 PM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
>
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Updating to 2.13.0, so we can pick up the latest -stable and
> support for 5.14+ kernels.
>
> We refresh one patch for new context, and update the LICENSE
> checksum due to commit 2df37e95fa4303 [Cleanup: Move headers from
> toplevel to include/lttng/]. which impacted the LICENSE file (but
> licensing is the same).

I'm seeing a build failure with this new LTTng and CONFIG_TRACEPOINTS
not enabled on the kernel 5.13.12. The failure comes from the Kbuild,
which does not demote the missing trace point config option from error
to warning. There is a patch file already in the layer, but it is only
appended to the 'class-devupstream' and is missing in the SRC_URI.

I was going to submit the patch to recipe to have it included, but
testing the build stage with this patch included I'm seeing a lot of
other errors then, something like:

lttng-modules-2.13.0/src/lttng-tracepoint.c:227:36: error: 'struct
module' has no member named 'num_tracepoints'
-- or --
src/probes/../../include/instrumentation/events/rpc.h:208:36: error:
implicit declaration of function 'rpc_qname'
[-Werror=implicit-function-declaration]

and the list goes on... :/

Have you seen this during testing of this new version? Any advise on
where to look next?

>
> MODULES_MODULE_SYMVERS_LOCATION must also be specified in this
> release, as the lttng build has moved the module target to a
> 'src' subdirectory.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> ---
>  ...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 32 ++++++-------------
>  ...ules_2.12.6.bb => lttng-modules_2.13.0.bb} |  6 ++--
>  2 files changed, 14 insertions(+), 24 deletions(-)
>  rename meta/recipes-kernel/lttng/{lttng-modules_2.12.6.bb => lttng-modules_2.13.0.bb} (88%)
>
>


-- 
Regards,
Andrey.

  reply	other threads:[~2021-08-20 11:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 15:27 [PATCH 0/4] linux-yocto-dev: dev and supporting recipes updates Bruce Ashfield
2021-08-17 15:27 ` [PATCH 1/4] linux-yocto-dev: bump to v5.14+ Bruce Ashfield
2021-08-17 15:27 ` [PATCH 2/4] lttng-modules: update to 2.13.0 Bruce Ashfield
2021-08-20 11:13   ` Andrey Zhizhikin [this message]
2021-08-20 12:57     ` [OE-core] " Bruce Ashfield
2021-08-20 13:21       ` Andrey Zhizhikin
2021-08-20 14:03         ` Andrey Zhizhikin
2021-08-20 14:10           ` Bruce Ashfield
2021-08-17 15:27 ` [PATCH 3/4] kernel-devsrc: 5.14+ updates Bruce Ashfield
2021-08-17 15:27 ` [PATCH 4/4] kernel-devsrc: fix 5.14+ objtool compilation Bruce Ashfield

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=CAHtQpK4rAfAjB7dwXoz4D42887whGu5xgrxGcCxKRYmNUiE3-Q@mail.gmail.com \
    --to=andrey.z@gmail.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.