From: Max Krummenacher <max.oss.09@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: bruce.ashfield@gmail.com, raj.khem@gmail.com,
quaresma.jose@gmail.com,
Max Krummenacher <max.krummenacher@toradex.com>
Subject: [OE-core][Patch v3 0/3] perf: add libtraceevent packageconfig
Date: Thu, 11 May 2023 14:56:00 +0200 [thread overview]
Message-ID: <20230511125603.958144-1-max.oss.09@gmail.com> (raw)
From: Max Krummenacher <max.krummenacher@toradex.com>
With kernel 6.4-rc1 commit 6898e60f709b ("perf build: If libtraceevent
isn't present error the build") having libtraceevent is a required
dependency unless building it with 'NO_LIBTRACEEVENT=1'.
Changes in V2
- add a patch importing libtraceevent from meta-openembedded
- move the pkg-config changes in a separate commit
- default to setting the packageconfig as we now have the dependecy in core
Changes in V3
- add Bruce as the maintainer of the new recipe libtraceevent, thanks Bruce.
Max Krummenacher (3):
libtraceevent: import from meta-openembedded
perf: make pkg-config available
perf: add libtraceevent packageconfig
meta/conf/distro/include/maintainers.inc | 1 +
...not-preserve-ownership-in-cp-command.patch | 40 +++++++++++++++++++
.../libtraceevent/libtraceevent_1.7.2.bb | 25 ++++++++++++
meta/recipes-kernel/perf/perf.bb | 5 ++-
4 files changed, 70 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-kernel/libtraceevent/libtraceevent/0001-makefile-Do-not-preserve-ownership-in-cp-command.patch
create mode 100644 meta/recipes-kernel/libtraceevent/libtraceevent_1.7.2.bb
--
2.35.3
next reply other threads:[~2023-05-11 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 12:56 Max Krummenacher [this message]
2023-05-11 12:56 ` [OE-core][Patch v3 1/3] libtraceevent: import from meta-openembedded Max Krummenacher
2023-05-11 19:59 ` Alexandre Belloni
2023-05-11 12:56 ` [OE-core][Patch v3 2/3] perf: make pkg-config available Max Krummenacher
2023-05-11 12:56 ` [OE-core][Patch v3 3/3] perf: add libtraceevent packageconfig Max Krummenacher
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=20230511125603.958144-1-max.oss.09@gmail.com \
--to=max.oss.09@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=max.krummenacher@toradex.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=quaresma.jose@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox