From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [git commit] configs/pc_x86_64_{bios, efi}_defconfig: add midding libelf kernel dependency
Date: Wed, 13 Sep 2023 08:59:54 +0200 [thread overview]
Message-ID: <871qf25zit.fsf@48ers.dk> (raw)
In-Reply-To: <20230820214028.01C8B85EF4@busybox.osuosl.org> (Thomas Petazzoni via buildroot's message of "Sun, 20 Aug 2023 23:38:44 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=b661f635b5cc08ded6ab14c19f2370c9f478e52e
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> objtool built by the kernel requires libelf
> ldd output/build/linux-6.1.24/tools/objtool/objtool
> linux-vdso.so.1
> libelf.so.1 => output/host/lib/libelf.so.1
> While updating the kernel [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] d45538f2e7acc1b330b191d559a81e8c1a961648
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4889436869
> https://gitlab.com/buildroot.org/buildroot/-/jobs/4889436872
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-13 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 21:38 [Buildroot] [git commit] configs/pc_x86_64_{bios, efi}_defconfig: add midding libelf kernel dependency Thomas Petazzoni via buildroot
2023-09-13 6:59 ` Peter Korsgaard [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=871qf25zit.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.