From: "Yakov Lerner" <iler.ml@gmail.com>
To: Santi <sbejar@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH] auto-detect changed $prefix in Makefile and properly rebuild to avoid broken install
Date: Thu, 15 Jun 2006 11:40:50 +0000 [thread overview]
Message-ID: <f36b08ee0606150440l544455c7r5c52609b360d0f74@mail.gmail.com> (raw)
In-Reply-To: <8aa486160606150426q19b0a661s@mail.gmail.com>
On 6/15/06, Santi <sbejar@gmail.com> wrote:
> Wed, 14 Jun 2006 22:26 +0300, Yakov Lerner <iler.ml@gmail.com>:
> > Many times, I mistakenly used 'make prefix=... install' where prefix value
> > was different from prefix value during build. This resulted in broken
> > install. This patch adds auto-detection of $prefix change to the Makefile.
> > This results in correct install whenever prefix is changed.
>
> I do this each time I install packages from source. I keep them with
> "stow" and the usual sequence is:
>
> make prefix=/home/santi/usr
> make install prefix=/home/santi/usr/stow/git
> cd /home/santi/usr/stow/
> stow -v git
>
> so with this auto-detection I'll compile some programs twice.
I'm not familiar with stow. Does stow create some kind of symlinks from
/home/santi/usr/stow/git to home/santi/usr ? If so, why can't you
use prefix=/home/santi/usr/stow/git both in 'make' and in 'make install' ?
Would this work ?
BTW, is it possible to have git use argv[0] to automatically determine
the executable_dir without compiled-in paths ?
Yakov
next prev parent reply other threads:[~2006-06-15 11:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 19:26 [PATCH] auto-detect changed $prefix in Makefile and properly rebuild to avoid broken install Yakov Lerner
2006-06-14 20:04 ` Junio C Hamano
2006-06-14 20:30 ` Yakov Lerner
2006-06-14 21:32 ` Junio C Hamano
2006-06-14 21:38 ` Yakov Lerner
2006-06-15 9:26 ` Matthias Lederhofer
2006-06-15 11:11 ` Yakov Lerner
2006-06-18 13:31 ` Petr Baudis
2006-06-15 11:26 ` Santi
2006-06-15 11:40 ` Yakov Lerner [this message]
2006-06-15 12:49 ` Santi
2006-06-15 13:00 ` Alexander Litvinov
2006-06-17 5:28 ` Junio C Hamano
2006-06-17 5:26 ` Junio C Hamano
2006-06-18 11:24 ` Karl Hasselström
2006-06-18 11:47 ` Junio C Hamano
2006-06-18 14:44 ` Karl Hasselström
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=f36b08ee0606150440l544455c7r5c52609b360d0f74@mail.gmail.com \
--to=iler.ml@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbejar@gmail.com \
/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).