public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Changqing Li <changqing.li@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] qemu-system-native: disable libkeyutils
Date: Tue, 23 Dec 2025 10:42:47 +0800	[thread overview]
Message-ID: <387c47b2-141e-46f1-812c-97e498e22ec0@windriver.com> (raw)
In-Reply-To: <CANNYZj-BHgRk3yja0hr3AabwZXwB0biFXMQQ73mxua=yAufH1w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]


On 12/22/25 19:09, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Mon, 22 Dec 2025 at 10:14, Changqing Li via lists.openembedded.org
> <changqing.li=windriver.com@lists.openembedded.org> wrote:
>> -EXTRA_OECONF:append = " --target-list=${@get_qemu_system_target_list(d)}"
>> +EXTRA_OECONF:append = " --target-list=${@get_qemu_system_target_list(d)} --disable-libkeyutils"
>>
>>   PACKAGECONFIG ??= "fdt alsa kvm pie slirp png pixman sdl \
>>       ${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'virglrenderer epoxy', '', d)} \
> It's better to add a PACKAGECONFIG for this. It will be disabled by
> default then.

Thanks,  it should be better,  I will send a V2.  My original idea is 
only disable libkeyutils for qemu-system-native and keep

original behavior for other recipes.

//Changqing

> Alex

[-- Attachment #2: Type: text/html, Size: 1976 bytes --]

      reply	other threads:[~2025-12-23  2:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22  9:13 [PATCH] qemu-system-native: disable libkeyutils changqing.li
2025-12-22 11:09 ` [OE-core] " Alexander Kanavin
2025-12-23  2:42   ` Changqing Li [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=387c47b2-141e-46f1-812c-97e498e22ec0@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=alex.kanavin@gmail.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