From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Ross Burton" <ross.burton@arm.com>
Cc: openembedded-core@lists.openembedded.org, nd@arm.com
Subject: Re: [OE-core] [PATCH] libtraceevent: build with Meson
Date: Mon, 28 Aug 2023 18:02:41 +0200 [thread overview]
Message-ID: <20230828180241.6d322d91@booty> (raw)
In-Reply-To: <20230827195744.3451852-1-ross.burton@arm.com>
Hello,
On Sun, 27 Aug 2023 20:57:44 +0100
"Ross Burton" <ross.burton@arm.com> wrote:
> From: Ross Burton <ross.burton@arm.com>
>
> After what I presume is the recent kernel upgrade, perf started to fail
> to configure. This was actually due to libtraceevent racing during its
> build and failing to put one of the .o files into the .so (reminder:
> Make is terrible). This doesn't cause the libtraceevent build to fail so
> once the broken .so is in sstate, it causes all future perf builds to
> fail.
>
> Instead of rewriting the Makefile rules to fix this race it's easier to
> switch to Meson which doesn't have this sort of problem. However the
> Meson support is pretty new and has some rough edges, so we need a patch
> to make it do the right thing.
>
> I will submit the libtraceevent fixes upstream shortly.
>
> [ YOCTO #15201 ]
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
The build I had run and that had been consistently failing has succeeded
after applying this patch!
Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-08-28 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 19:57 [PATCH] libtraceevent: build with Meson ross.burton
2023-08-28 16:02 ` Luca Ceresoli [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=20230828180241.6d322d91@booty \
--to=luca.ceresoli@bootlin.com \
--cc=nd@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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.