Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	Petr Vorel <petr.vorel@gmail.com>
Subject: Re: [Buildroot] [PATCH v4 4/5] package/quota: fix build failure due to missing BR2_PACKAGE_LIBTIRPC_RPCDB
Date: Tue, 6 Jan 2026 23:22:43 +0100	[thread overview]
Message-ID: <20260106232243.0a97bcd4@windsurf> (raw)
In-Reply-To: <20260103132552.3979708-5-bernd@kuhls.net>

On Sat,  3 Jan 2026 14:25:51 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:

> Package quota requires libtirpc rpcdb option enabled with non-glibc
> toolchains since the bump of libtirpc to version 1.3.7 with buildroot
> commit 3f3d6e43de9b4aac7df8545fd811171256f878d3 which includes upstream
> commit:
> https://git.linux-nfs.org/?p=steved/libtirpc.git;a=commit;h=7cea8ad66aecc21e6caae330b5d31075af399193
> 
> These build errors, caused by the forementioned upstream commit, only
> occur with non-glibc toolchains:
> https://patchwork.yoctoproject.org/comment/30091/
> "but I believe it breaks the build with musl"
> as shown by our autobuilders:
> 
> https://autobuild.buildroot.net/?reason=quota-4.10
> 
> Fixes:
> https://autobuild.buildroot.net/results/fb0/fb0adbb7687d8db4228e2fc1ce7a7272486fd3ef/
> "svc_socket.c:(.text+0x2c): undefined reference to `getrpcbynumber'"
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
>  package/quota/Config.in | 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

  reply	other threads:[~2026-01-06 22:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-03 13:25 [Buildroot] [PATCH v4 0/5] package/libtirpc: introduce BR2_PACKAGE_LIBTIRPC_RPCDB Bernd Kuhls
2026-01-03 13:25 ` [Buildroot] [PATCH v4 1/5] " Bernd Kuhls
2026-01-06 22:21   ` Thomas Petazzoni via buildroot
2026-01-19 10:09   ` Arnout Vandecappelle via buildroot
2026-01-03 13:25 ` [Buildroot] [PATCH v4 2/5] package/nfs-utils: fix build failure due to missing BR2_PACKAGE_LIBTIRPC_RPCDB Bernd Kuhls
2026-01-06 22:22   ` Thomas Petazzoni via buildroot
2026-01-19 10:09   ` Arnout Vandecappelle via buildroot
2026-01-03 13:25 ` [Buildroot] [PATCH v4 3/5] package/rpcbind: " Bernd Kuhls
2026-01-06 22:22   ` Thomas Petazzoni via buildroot
2026-01-19 10:09   ` Arnout Vandecappelle via buildroot
2026-01-03 13:25 ` [Buildroot] [PATCH v4 4/5] package/quota: " Bernd Kuhls
2026-01-06 22:22   ` Thomas Petazzoni via buildroot [this message]
2026-01-03 13:25 ` [Buildroot] [PATCH v4 5/5] package/snort3: " Bernd Kuhls
2026-01-06 22:22   ` Thomas Petazzoni via buildroot

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=20260106232243.0a97bcd4@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=fontaine.fabrice@gmail.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=jarkko@kernel.org \
    --cc=petr.vorel@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