All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: fstests@vger.kernel.org, zlang@kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 4/4] xfstests: fix permissions on system file installed by libtoolize
Date: Fri, 25 Sep 2026 13:04:55 -0700	[thread overview]
Message-ID: <20260925200455.GO6253@frogsfrogsfrogs> (raw)
In-Reply-To: <20260925104514.664260-5-aalbersh@kernel.org>

On Fri, Sep 25, 2026 at 12:45:12PM +0200, Andrey Albershteyn wrote:
> Libtoolize installs set of auxiliary 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 will fail.
> 
> Fix this by setting permission explicitly on files copied by libtoolize.
> 
> See similar commit in xfsprogs:
> 6b32423addd2 ("xfsprogs: fix permissions on files installed by libtoolize")
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>

Looks ok,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
>  Makefile | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/Makefile b/Makefile
> index a48d8d62f038..6c3de609bf38 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -76,6 +76,9 @@ endif
>  
>  configure: configure.ac
>  	libtoolize -cfi
> +	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
>  	autoheader
> -- 
> 2.54.0
> 
> 

  reply	other threads:[~2026-09-25 20:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 10:45 [PATCH v3 0/4] xfstests: random fixes Andrey Albershteyn
2026-09-25 10:45 ` [PATCH v3 1/4] xfs/071: use _link_out_link instead of opencoding file picking Andrey Albershteyn
2026-09-25 20:03   ` Darrick J. Wong
2026-09-25 10:45 ` [PATCH v3 2/4] common: link .out file to the output directory Andrey Albershteyn
2026-09-25 20:04   ` Darrick J. Wong
2026-09-25 10:45 ` [PATCH v3 3/4] generic/452: make coping work with multi-call binary Andrey Albershteyn
2026-09-25 20:02   ` Darrick J. Wong
2026-09-25 10:45 ` [PATCH v3 4/4] xfstests: fix permissions on system file installed by libtoolize Andrey Albershteyn
2026-09-25 20:04   ` Darrick J. Wong [this message]
2026-09-27 11:50 ` [PATCH v3 0/4] xfstests: random fixes Zorro Lang

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=20260925200455.GO6253@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=zlang@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 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.