public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: linux-xfs@vger.kernel.org, aalbersh@kernel.org
Subject: Re: [PATCH 1/2] xfsprogs: fix permissions on files installed by libtoolize
Date: Fri, 27 Sep 2024 08:17:09 -0700	[thread overview]
Message-ID: <20240927151709.GK21853@frogsfrogsfrogs> (raw)
In-Reply-To: <20240927134142.200642-3-aalbersh@redhat.com>

On Fri, Sep 27, 2024 at 03:41:42PM +0200, Andrey Albershteyn wrote:
> 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.

Does cp -f include/install-sh . work for this?

Aside from the install script, the build system doesn't modify any of
the files that come in from libtol, does it?

--D

> Fix this by setting permission explicitly on files copied by
> libtoolize.
> 
> Signed-off-by: Andrey Albershteyn <aalbersh@redhat.com>
> ---
>  Makefile | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Makefile b/Makefile
> index 4e768526c6fe..11cace1112e6 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -109,6 +109,8 @@ endif
>  
>  configure: configure.ac
>  	libtoolize -c -i -f
> +	chmod 755 config.guess config.sub install-sh
> +	chmod 644 ltmain.sh m4/{libtool,ltoptions,ltsugar,ltversion,lt~obsolete}.m4
>  	cp include/install-sh .
>  	aclocal -I m4
>  	autoconf
> -- 
> 2.44.1
> 
> 

  reply	other threads:[~2024-09-27 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 13:41 [PATCH 0/2] Minor fixes for xfsprogs Andrey Albershteyn
2024-09-27 13:41 ` [PATCH 1/2] xfsprogs: fix permissions on files installed by libtoolize Andrey Albershteyn
2024-09-27 15:17   ` Darrick J. Wong [this message]
2024-09-27 15:29     ` Andrey Albershteyn
2024-09-27 13:41 ` [PATCH 2/2] xfsprogs: update gitignore Andrey Albershteyn
2024-09-27 14:09   ` Carlos Maiolino
2024-09-27 14:17     ` Andrey Albershteyn
2024-09-27 16:17       ` Andrey Albershteyn
2024-09-27 15:20   ` Darrick J. Wong
2024-09-27 16:14     ` Andrey Albershteyn

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=20240927151709.GK21853@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=aalbersh@redhat.com \
    --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