From: Jeff King <peff@peff.net>
To: mlell@posteo.de
Cc: git@vger.kernel.org
Subject: Re: Bug: Install from .tar.xz fails without write permission on /usr/local/share/man/man3
Date: Fri, 1 Jun 2018 02:33:14 -0400 [thread overview]
Message-ID: <20180601063314.GA2170@sigill.intra.peff.net> (raw)
In-Reply-To: <d464115b7c2ee5f9084ae9bd33cebea1@posteo.de>
On Thu, May 31, 2018 at 06:30:18PM +0200, mlell@posteo.de wrote:
> I was trying to build git 2.9.5 as a normal user, as I have no root access
> on a cluster with outdated software.
>
> The build fails, unless I change the PREFIX=/usr/local line in
> per/perl.mak:80 to a folder where I have write permission.
> Apparently, perl.mak does not honour the --prefix= setting of ./configure.
Weird, I can't reproduce. That perl.mak is generated by running
Makefile.PL.
If I follow your steps:
> wget https://mirrors.edge.kernel.org/pub/software/scm/git/git-2.9.5.tar.xz
> tar xf git-2.9.5.tar.xz
> cd git-2.9.5
> ./configure --prefix=$HOME/.usr
> make
During this step I get output like this (amidst the other compiles):
/usr/bin/perl Makefile.PL PREFIX='/tmp/foo' INSTALL_BASE='' --localedir='/tmp/foo/share/locale'
Generating a Unix-style perl.mak
Writing perl.mak for Git
So I wonder if there is some reason your perl MakeMaker module is not
behaving the same way.
At any rate, though, I don't know if it's worth digging too far. Git
v2.17 drastically simplified the perl section of the build process,
ditching MakeMaker completely. The new code is much simpler and follows
the same prefix rules as the rest of the Makefile. So probably the
simplest thing is try v2.17.1.
-Peff
prev parent reply other threads:[~2018-06-01 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 16:30 Bug: Install from .tar.xz fails without write permission on /usr/local/share/man/man3 mlell
2018-05-31 18:33 ` Christian Couder
2018-06-01 6:33 ` Jeff King [this message]
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=20180601063314.GA2170@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=mlell@posteo.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;
as well as URLs for NNTP newsgroup(s).