From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <Qi.Chen@windriver.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH] shadow: upgrade from 4.18.0 to 4.19.3
Date: Tue, 10 Feb 2026 16:46:20 +0100 [thread overview]
Message-ID: <DGBED9UTZVK0.2P2KE59AW872@bootlin.com> (raw)
In-Reply-To: <20260210044850.2866022-1-Qi.Chen@windriver.com>
On Tue Feb 10, 2026 at 5:48 AM CET, Chen Qi via lists.openembedded.org wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> The major changes in 4.19.x:
> https://github.com/shadow-maint/shadow/releases/tag/4.19.0
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
Hi Chen,
Thanks for the upgrade.
It looks like this version fails to compile. Given the error and the
fact that it builds on some machines, maybe it is linked with the host
gcc version?
ERROR: shadow-native-4.19.3-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/shadow-native/4.19.3/temp/run.do_compile.674478' failed with exit code 1
...
| ../../sources/shadow-4.19.3/lib/sssd.h:14:18: error: parameter name omitted
| 14 | sssd_flush_cache(int)
| | ^~~
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/3175
So yes, we have a static inline function that takes one parameter but
does not use it. And the compiler is not happy as it is not named.
Can you have a look at that? Maybe there is already a fix upstream or
one could be submitted.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-02-10 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 4:48 [OE-core][PATCH] shadow: upgrade from 4.18.0 to 4.19.3 Qi.Chen
2026-02-10 15:46 ` Mathieu Dubois-Briand [this message]
2026-02-11 2:37 ` ChenQi
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=DGBED9UTZVK0.2P2KE59AW872@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox