From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org, Petr Vorel <petr.vorel@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 2/2] pacakge/nfs-utils: fix build failure due to missing BR2_PACKAGE_LIBTIRPC_DB
Date: Sat, 13 Dec 2025 18:14:23 +0100 [thread overview]
Message-ID: <20251213181423.3a3d23a6@windsurf> (raw)
In-Reply-To: <20251213151730.821513-2-giulio.benetti@benettiengineering.com>
Hello,
On Sat, 13 Dec 2025 16:17:30 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Pacakge nfs-utils requires libtirpc rpcdb option, so let's select it by
^^^^^^ minor typo
Since when is this needed? When fixing an autobuilder issue, we need to
understand what introduced the problem so that we know whether the fix
needs to be backported or not.
Thanks a lot!
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:[~2025-12-13 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 15:17 [Buildroot] [PATCH v2 1/2] package/libtirpc: introduce BR2_PACKAGE_LIBTIRPC_DB Giulio Benetti
2025-12-13 15:17 ` [Buildroot] [PATCH v2 2/2] pacakge/nfs-utils: fix build failure due to missing BR2_PACKAGE_LIBTIRPC_DB Giulio Benetti
2025-12-13 17:14 ` Thomas Petazzoni via buildroot [this message]
2025-12-13 18:39 ` Petr Vorel
2025-12-13 17:55 ` Thomas Petazzoni via buildroot
2025-12-13 18:04 ` Giulio Benetti
2025-12-13 18:51 ` Petr Vorel
2025-12-13 17:26 ` [Buildroot] [PATCH v2 1/2] package/libtirpc: introduce BR2_PACKAGE_LIBTIRPC_DB Thomas Petazzoni via buildroot
2025-12-13 18:36 ` Petr Vorel
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=20251213181423.3a3d23a6@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--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