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 3/5] package/rpcbind: fix build failure due to missing BR2_PACKAGE_LIBTIRPC_RPCDB
Date: Tue, 6 Jan 2026 23:22:30 +0100 [thread overview]
Message-ID: <20260106232230.28cc9df4@windsurf> (raw)
In-Reply-To: <20260103132552.3979708-4-bernd@kuhls.net>
On Sat, 3 Jan 2026 14:25:50 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> diff --git a/package/rpcbind/Config.in b/package/rpcbind/Config.in
> index 9cde7bba39..0b2c207580 100644
> --- a/package/rpcbind/Config.in
> +++ b/package/rpcbind/Config.in
> @@ -5,6 +5,7 @@ config BR2_PACKAGE_RPCBIND
> depends on BR2_TOOLCHAIN_HAS_THREADS # libtirpc
> depends on BR2_USE_MMU # fork()
> select BR2_PACKAGE_LIBTIRPC
> + select BR2_PACKAGE_LIBTIRPC_RPCDB if !BR2_TOOLCHAIN_USES_GLIBC
Same as nfs-utils, dropped " if !BR2_TOOLCHAIN_USES_GLIBC", and applied.
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-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 [this message]
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
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=20260106232230.28cc9df4@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