From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <victor.kamensky7@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] systemtap: upgrade 5.3 -> 5.4
Date: Mon, 22 Dec 2025 09:21:18 +0100 [thread overview]
Message-ID: <DF4LLAR0AM9L.1NMHO4TTMJ27O@bootlin.com> (raw)
In-Reply-To: <20251221072824.3981-1-victor.kamensky7@gmail.com>
On Sun Dec 21, 2025 at 8:28 AM CET, Victor Kamensky via lists.openembedded.org wrote:
> * removed upstreamed patch
> * fixed patch fuzz issue
>
> Signed-off-by: Victor Kamensky <victor.kamensky7@gmail.com>
> ---
Hi Victor,
Thanks for your patch.
It look like the build is failing on various platforms:
ERROR: systemtap-5.4-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/qemux86/build/build/tmp/work/core2-32-poky-linux/systemtap/5.4/temp/run.do_compile.1003148' failed with exit code 1
...
| In file included from ../sources/systemtap-5.4/staptree.h:27,
| from ../sources/systemtap-5.4/elaborate.h:12,
| from ../sources/systemtap-5.4/elaborate.cxx:11:
| ../sources/systemtap-5.4/elaborate.cxx: In member function 'virtual void const_folder::visit_defined_op(defined_op*)':
| ../sources/systemtap-5.4/elaborate.cxx:5119:33: error: format '%ld' expects argument of type 'long int', but argument 2 has type 'int64_t' {aka 'long long int'} [-Werror=format=]
| 5119 | session.print_warning (_F("Collapsing unresolved @define to %ld [stapprobes]", value), e->tok);
| | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| ../sources/systemtap-5.4/staputil.h:54:27: note: in definition of macro '_'
| 54 | #define _(string) gettext(string)
https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/2874
https://autobuilder.yoctoproject.org/valkyrie/#/builders/16/builds/2926
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/2738
https://autobuilder.yoctoproject.org/valkyrie/#/builders/20/builds/2867
https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/2904
https://autobuilder.yoctoproject.org/valkyrie/#/builders/74/builds/2878
Can you have a look at this issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-12-22 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 7:28 [PATCH] systemtap: upgrade 5.3 -> 5.4 Victor Kamensky
2025-12-22 8:21 ` Mathieu Dubois-Briand [this message]
2025-12-26 2:58 ` [OE-core] " Victor Kamensky
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=DF4LLAR0AM9L.1NMHO4TTMJ27O@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=victor.kamensky7@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