From: Phillip Susi <psusi@ubuntu.com>
To: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
Cc: git@vger.kernel.org
Subject: Re: make install rewrites source files
Date: Mon, 23 Jan 2012 15:28:39 -0500 [thread overview]
Message-ID: <4F1DC2F7.2070502@ubuntu.com> (raw)
In-Reply-To: <hbf.20120123bz2f@bombur.uio.no>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/23/2012 9:18 AM, Hallvard Breien Furuseth wrote:
> INSTALL says we can install a profiled Git with $ make profile-all
> # make install prefix=...
prefix should be an argument to configure, not make.
> This does not work: 'make install' notices that the build flags
> has changed and rebuilds Git - presumably without using the profile
> info. The patch below fixes this.
make install implicitly includes make all; it is supposed to rebuild
anything that needs rebuilt.
> However, make install should not write to the source directory in
> any case. That fails as root if root lacks write access there, due
> to NFS mounts that map root to nobody etc. At least git-instaweb
> and GIT-BUILD-OPTIONS are rewritten. You can simulate this with su
> nobody -s /bin/bash -c 'make -k install' after configuring with
> prefix=<directory owned by nobody>.
If you want to build locally from a read only nfs mount, then you
should run the configure script in a local directory:
mkdir /tmp/build
cd /tmp/build
/path/to/nfs/source/configure
make
make install
> Index: Makefile --- Makefile~ 2012-01-19 01:36:02.000000000 +0100
> +++ Makefile 2012-01-23 14:44:56.554980323 +0100
Hrm... Makefile should itself be a generated file from Makefile.in or
Makefile.am, but it appears that git isn't doing this. Perhaps that
should be fixed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPHcL3AAoJEJrBOlT6nu759U8IANCtJDWnCizSDWrJAFWe3ISr
FemiFgW347qjLcWlJS036nPfKnrxrJ88rF2e9+8Tj/hfPojNwCmyvN7rz+guI0uA
qqOfk9uN38Qd/jwfW5gv/7raKP4eUyRZ9ioptX3NqQtP5Co4TFuajOfswpN8f/DL
QiU7os62Df5HWW2U8A3XT9KiU9oWRala8dcrp5EJkEOfYDvQG2o3e1N/D91KC4el
lAyVEnzrvoLr5NzHCnFe7dQqvAB2S3PE/NP4anZHyNRp3SDLu1iZbD9MKC21Bd3n
BmCn9Vh7U+reC/NBMq8qaM69jLRk2Dx12brFoyY5/cjdQuaLj+n6h1nN9MqSKYI=
=/qLy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-01-23 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 14:18 make install rewrites source files Hallvard Breien Furuseth
2012-01-23 20:15 ` Junio C Hamano
2012-01-23 20:57 ` Hallvard Breien Furuseth
2012-01-26 22:52 ` Clemens Buchacher
2012-01-27 0:49 ` Junio C Hamano
2012-01-27 13:11 ` Hallvard Breien Furuseth
2012-01-23 20:28 ` Phillip Susi [this message]
2012-01-23 20:52 ` Junio C Hamano
2012-01-27 9:46 ` Hallvard B Furuseth
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=4F1DC2F7.2070502@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=git@vger.kernel.org \
--cc=h.b.furuseth@usit.uio.no \
/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).