mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bastian Krause <bst@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: [ptxdist] [PATCH] fuse3: fix copy/paste error selecting an option from fuse instead of fuse3
Date: Fri, 24 Jun 2022 12:06:33 +0200	[thread overview]
Message-ID: <20220624100633.3198888-1-bst@pengutronix.de> (raw)

Separate packages for fuse and fuse3 exist. fuse3 was copied from fuse. A
previous commit 91d340dec ("fuse3: fix copy/paste error") fixed
copy/paste errors, but there is another one configuring the utils
option:

If FUSE and FUSE_UTIL are not selected, fuse3's utils are not built
resulting in targetinstall errors for fusermount3, mount.fuse3 and
99-fuse3.rules. This again is only triggered since 91d340dec
("fuse3: fix copy/paste error"). Before that, no meson build options
were provided, so the default utils=true was used.

Since fuse3's tools and library were always installed unconditionally,
just enable the utils option unconditionally.

Signed-off-by: Bastian Krause <bst@pengutronix.de>
---
 rules/fuse3.make | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rules/fuse3.make b/rules/fuse3.make
index 8af8f7282..d4925f2dd 100644
--- a/rules/fuse3.make
+++ b/rules/fuse3.make
@@ -36,7 +36,7 @@ FUSE3_CONF_OPT	:= \
 	-Ddisable-mtab=true \
 	-Dexamples=false \
 	-Dudevrulesdir=/usr/lib/udev/rules.d \
-	-Dutils=$(call ptx/truefalse,PTXCONF_FUSE_UTIL)
+	-Dutils=true
 
 # ----------------------------------------------------------------------------
 # Target-Install
-- 
2.30.2




             reply	other threads:[~2022-06-24 10:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 10:06 Bastian Krause [this message]
2022-07-01  5:10 ` [ptxdist] [APPLIED] " Michael Olbrich

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=20220624100633.3198888-1-bst@pengutronix.de \
    --to=bst@pengutronix.de \
    --cc=ptxdist@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