From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Joseph Kogut <joseph@anodize.com>
Cc: buildroot@buildroot.org, joseph.kogut@gmail.com
Subject: Re: [Buildroot] [PATCH 2/2] package/passt: bump to version 2026_07_28.f8df3f1
Date: Sun, 6 Sep 2026 23:15:39 +0200 [thread overview]
Message-ID: <ap3Xvv4F7Mgi3mve@windsurf> (raw)
In-Reply-To: <20260818-passt-20260728-v1-2-aa8bc1ce2c5a@anodize.com>
Hello Joseph,
On Tue, Aug 18, 2026 at 01:55:34PM -0700, Joseph Kogut wrote:
> Signed-off-by: Joseph Kogut <joseph@anodize.com>
> ---
> package/passt/passt.hash | 2 +-
> package/passt/passt.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Thanks for this patch. With this version bump, the build fails with:
isolation.c: In function ‘isolate_fds’:
isolation.c:277:13: error: implicit declaration of function ‘close_range’; did you mean ‘SYS_close_range’? [-Wimplicit-function-declaration]
277 | if (close_range(close_from, ~0U, CLOSE_RANGE_UNSHARE)) {
| ^~~~~~~~~~~
| SYS_close_range
isolation.c:277:42: error: ‘CLOSE_RANGE_UNSHARE’ undeclared (first use in this function)
277 | if (close_range(close_from, ~0U, CLOSE_RANGE_UNSHARE)) {
| ^~~~~~~~~~~~~~~~~~~
isolation.c:277:42: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [Makefile:103: passt] Error 1
make[1]: Leaving directory '/home/thomas/projets/buildroot/output/build/passt-2026_07_28.f8df3f1'
make: *** [package/pkg-generic.mk:273: /home/thomas/projets/buildroot/output/build/passt-2026_07_28.f8df3f1/.stamp_built] Error 2
With the following configuration:
BR2_aarch64=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_AARCH64_MUSL_BLEEDING_EDGE=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_PODMAN=y
# BR2_TARGET_ROOTFS_TAR is not set
Note that I didn't try _before_ the bump, so I am not 100% sure the
build issue is caused by the bump.
Could you have a look?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-06 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 20:55 [Buildroot] [PATCH 0/2] package/passt: dependency fixes and version bump Joseph Kogut
2026-08-18 20:55 ` [Buildroot] [PATCH 1/2] package/passt: disable on uclibc Joseph Kogut
2026-09-07 6:08 ` Thomas Petazzoni via buildroot
2026-08-18 20:55 ` [Buildroot] [PATCH 2/2] package/passt: bump to version 2026_07_28.f8df3f1 Joseph Kogut
2026-09-06 21:15 ` Thomas Petazzoni via buildroot [this message]
2026-09-07 6:02 ` Thomas Petazzoni via buildroot
2026-09-07 20:23 ` Joseph Kogut
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=ap3Xvv4F7Mgi3mve@windsurf \
--to=buildroot@buildroot.org \
--cc=joseph.kogut@gmail.com \
--cc=joseph@anodize.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