From: Daniel Turull <daniel.turull@ericsson.com>
To: "yoann.congal@smile.fr" <yoann.congal@smile.fr>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [wrynose][PATCH] systemd-systemctl-native: disable libpam meson option
Date: Mon, 29 Jun 2026 10:12:48 +0000 [thread overview]
Message-ID: <6aeae8a4c115d6a60c82fad10b4832ec809b4a80.camel@ericsson.com> (raw)
In-Reply-To: <CAMSfU+5ipfW1CCFQ7=7ndWW1nQAsbaJcj9ditV9gwkPr=2sgfw@mail.gmail.com>
On Mon, 2026-06-29 at 11:51 +0200, Yoann Congal via
lists.openembedded.org wrote:
>
>
> Le lun. 29 juin 2026 à 10:42, Daniel Turull via
> lists.openembedded.org
> <daniel.turull=ericsson.com@lists.openembedded.org> a écrit :
> > From: Daniel Turull <daniel.turull@ericsson.com>
> >
> > When building on rhel8.10 we got the following crash during
> > do_compile
> >
> > systemctl-259.5/src/shared/pam-util.c
> > | ../sources/systemd-systemctl-259.5/src/shared/pam-util.c:3:10:
> > fatal error: security/pam_ext.h: No such file or directory
> > | 3 | #include <security/pam_ext.h>
> > | | ^~~~~~~~~~~~~~~~~~~~
> > | compilation terminated.
> > | ninja: build stopped: subcommand failed.
> > | INFO: autodetecting backend as ninja
> >
> > libpam is not needed for systemctl task done by bitbake, therfore
> > disable MESON option.
> >
> > Signed-off-by: Daniel Turull <daniel.turull@ericsson.com>
>
>
> Hello,
>
> What would be the corresponding master commit? "systemd: upgrade to
> 261"?
>
Yes.
I have tested the CVE fix in the rhel8 machine and I found the same
issue that when I did the systemd upgrade
Regards,
Daniel
>
> >
prev parent reply other threads:[~2026-06-29 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 8:41 [wrynose][PATCH] systemd-systemctl-native: disable libpam meson option daniel.turull
2026-06-29 9:51 ` [OE-core] " Yoann Congal
2026-06-29 10:12 ` Daniel Turull [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=6aeae8a4c115d6a60c82fad10b4832ec809b4a80.camel@ericsson.com \
--to=daniel.turull@ericsson.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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