From: Andrey Albershteyn <aalbersh@kernel.org>
To: linux-xfs@vger.kernel.org
Cc: Andrey Albershteyn <aalbersh@kernel.org>
Subject: [PATCH 1/2] xfsdump: fix permissions on files installed by libtoolize
Date: Wed, 6 May 2026 18:37:43 +0200 [thread overview]
Message-ID: <20260506163746.1083845-2-aalbersh@kernel.org> (raw)
In-Reply-To: <20260506163746.1083845-1-aalbersh@kernel.org>
Libtoolize installs some set of AUX files from its system package.
Not all distributions have the same permissions set on these files.
For example, read-only libtoolize system package will copy those
files without write permissions. This causes build to fail as next
line copies ./include/install-sh over ./install-sh which is not
writable.
Fix this by setting permission explicitly on files copied by
libtoolize.
The same fix in xfsprogs:
6b32423addd2 ("xfsprogs: fix permissions on files installed by libtoolize")
Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
---
Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Makefile b/Makefile
index e849c7fd6e16..36c7ace3d102 100644
--- a/Makefile
+++ b/Makefile
@@ -70,6 +70,9 @@ LIBTOOLIZE_INSTALL = `libtoolize -n -i >/dev/null 2>/dev/null && echo -i`
configure:
libtoolize -c $(LIBTOOLIZE_INSTALL) -f
+ chmod 755 config.guess config.sub install-sh
+ chmod 644 ltmain.sh m4/libtool.m4 m4/ltoptions.m4 m4/ltsugar.m4 \
+ m4/ltversion.m4 m4/lt~obsolete.m4
cp include/install-sh .
aclocal -I m4
autoconf
--
2.51.2
next prev parent reply other threads:[~2026-05-06 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 16:37 [PATCH 0/2] xfsdump: improve tooling Andrey Albershteyn
2026-05-06 16:37 ` Andrey Albershteyn [this message]
2026-05-07 5:34 ` [PATCH 1/2] xfsdump: fix permissions on files installed by libtoolize Christoph Hellwig
2026-05-06 16:37 ` [PATCH 2/2] xfsdump: update release.sh Andrey Albershteyn
2026-05-07 5:34 ` Christoph Hellwig
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=20260506163746.1083845-2-aalbersh@kernel.org \
--to=aalbersh@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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