From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] host-nfsutils: fix building without libsqlite3-dev
Date: Fri, 6 Feb 2026 09:56:13 +0100 [thread overview]
Message-ID: <20260206085613.90313-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260119-v2026-01-0-topic-host-nfsutils-v1-1-bba795aff830@pengutronix.de>
Thanks, applied as c95386734a26a847968da765dcb8d438bc8e9968.
Michael
[sent from post-receive hook]
On Fri, 06 Feb 2026 09:56:13 +0100, Steffen Trumtrar <s.trumtrar@pengutronix.de> wrote:
> The configure step checks if sqlite3-devel is available on the host system.
> nfs-utils needs sqlite3 for the nfsdcld which in turn is only needed for
> a nfs4 server. As the nfs4server is disabled, the library doesn't need
> to be available on the host.
>
> Disable the check, which results in an error when the library isn't
> available, by setting the check for a recent version to 'yes' and
> disabling all other sqlite3 checks.
>
> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> Message-Id: <20260119-v2026-01-0-topic-host-nfsutils-v1-1-bba795aff830@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/host-nfsutils.make b/rules/host-nfsutils.make
> index 5c734a269539..fc58eafbc21f 100644
> --- a/rules/host-nfsutils.make
> +++ b/rules/host-nfsutils.make
> @@ -18,7 +18,10 @@ HOST_PACKAGES-$(PTXCONF_HOST_NFSUTILS) += host-nfsutils
> # fake rpc/rpc.h availability, it's not needed for rpcgen
> HOST_NFSUTILS_CONF_ENV := \
> $(HOST_ENV) \
> - ac_cv_header_rpc_rpc_h=yes
> + ac_cv_header_rpc_rpc_h=yes \
> + ac_cv_header_sqlite3_h=no \
> + libsqlite3_cv_is_recent=yes \
> + ac_cv_lib_sqlite3_sqlite3_libversion=no
>
> #
> # autoconf
prev parent reply other threads:[~2026-02-06 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 7:59 [ptxdist] [PATCH] " Steffen Trumtrar
2026-02-06 8:56 ` Michael Olbrich [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=20260206085613.90313-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.trumtrar@pengutronix.de \
/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