From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] support/testing: TestSELinuxSystemd{Ext4, Squashfs} add midding libelf kernel dependency
Date: Sun, 30 Jul 2023 12:12:16 +0200 [thread overview]
Message-ID: <20230730121216.2d810766@windsurf> (raw)
In-Reply-To: <20230729231434.299864-1-romain.naour@gmail.com>
On Sun, 30 Jul 2023 01:14:34 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> objtool built by the kernel requires libelf
>
> ldd TestSELinuxSystemdExt4/build/linux-6.1.26/tools/objtool/objtool
> linux-vdso.so.1
> libelf.so.1 => TestSELinuxSystemdExt4/host/lib/libelf.so.1
>
> While updating the kernel used in TestSELinuxSystemd [1] we
> forgot to select BR2_LINUX_KERNEL_NEEDS_HOST_LIBELF to provide
> Buildroot's host-libelf. Using host-libelf avoid linking with
> libelf installed on the host or failing to build objtool if
> libelf is not installed.
>
> [1] 60b84fb7ce4612b2b14a675e28331111468e1f2b
>
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4725186370 (TestSELinuxSystemdSquashfs)
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4725186368 (TestSELinuxSystemdExt4)
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
> support/testing/tests/init/test_systemd_selinux.py | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-30 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 23:14 [Buildroot] [PATCH] support/testing: TestSELinuxSystemd{Ext4, Squashfs} add midding libelf kernel dependency Romain Naour
2023-07-30 10:12 ` Thomas Petazzoni via buildroot [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=20230730121216.2d810766@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.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