From: "Darrick J. Wong" <djwong@kernel.org>
To: Allen Hewes <rallenh@hotmail.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfsprogs: healer: install targets one at a time
Date: Tue, 14 Jul 2026 16:30:27 -0700 [thread overview]
Message-ID: <20260714233027.GL7380@frogsfrogsfrogs> (raw)
In-Reply-To: <3681cff200496f792a9f0dfdc117c268fc5803d5.camel@hotmail.com>
On Tue, Jul 14, 2026 at 11:21:03PM +0000, Allen Hewes wrote:
> libtool's --mode=install requires the destination to already exist
> as a real directory whenever more than one source file is given
> (it emulates cp/install semantics, which have the same requirement).
> Installing xfs_healer and xfs_healer_start in a single LTINSTALL
> call trips this check on any build where HAVE_HEALER_START_DEPS=yes,
> since PKG_LIBEXEC_DIR isn't guaranteed to exist under the raw,
> un-DESTDIR'd path libtool checks. Install each target separately
> to avoid the multi-file directory check entirely.
Aha, so that's the bug then -- distro build scripts set DESTDIR=/xxx and
run the build. include/buildefs sets
PKG_LIBEXEC_DIR=/usr/libexec/xfsprogs and passes that to libtool.
libtool sees that /usr/libexec/xfsprogs doesn't exist and fails.
Or, if that path happens to exist already, then it starts our custom
../install-sh script which copies the file to $DESTDIR/$PKG_LIBEXEC_DIR
which is NOT the same path that libtool dies on.
> Assisted-by: Claude:claude-sonnet-5
> Signed-off-by: Allen Hewes <rallenh@hotmail.com>
> ---
> healer/Makefile | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/healer/Makefile b/healer/Makefile
> index e3c41e66..4aa58757 100644
> --- a/healer/Makefile
> +++ b/healer/Makefile
> @@ -69,7 +69,9 @@ install: $(INSTALL_HEALER)
>
> install-healer: default
> $(INSTALL) -m 755 -d $(PKG_LIBEXEC_DIR)
> - $(LTINSTALL) -m 755 $(BUILD_TARGETS) $(PKG_LIBEXEC_DIR)
> + for f in $(BUILD_TARGETS); do \
> + $(LTINSTALL) -m 755 $$f $(PKG_LIBEXEC_DIR); \
Let's hope nobody ever wants to build a binary with a space in it.
Thanks for digging into this.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> + done
>
> install-systemd: default
> $(INSTALL) -m 755 -d $(SYSTEMD_SYSTEM_UNIT_DIR)
> --
> 2.55.0
>
next prev parent reply other threads:[~2026-07-14 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 23:21 [PATCH] xfsprogs: healer: install targets one at a time Allen Hewes
2026-07-14 23:30 ` Darrick J. Wong [this message]
2026-07-14 23:34 ` Allen Hewes
2026-07-14 23:48 ` Darrick J. Wong
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=20260714233027.GL7380@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rallenh@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.