git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Litvinov <lan@academsoft.ru>
To: Santi <sbejar@gmail.com>
Cc: "Yakov Lerner" <iler.ml@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 20:00:42 +0700	[thread overview]
Message-ID: <200606152000.43029.lan@academsoft.ru> (raw)
In-Reply-To: <8aa486160606150549n4b55912ap@mail.gmail.com>

> > If so, why can't you
> > use prefix=/home/santi/usr/stow/git both in 'make' and in 'make install'
> > ? Would this work ?
>
> For the few tests I've made it does works, but it is not the
> recommended method from the stow developers, and I suppose they know
> better than me.

I always use make prefix=/usr/local/stow/git-bla-bla and it works. The only 
thing that make break is the case when you install library into such prefix 
and it store it in the pkgconfig file. And when you will compile application 
it will be build with library paths set to /usr/local/stow/lib/libxyz and not 
to /usr/local/lib/libxyz.

But I dont make such big dependences from sources so it works.

  reply	other threads:[~2006-06-15 13:01 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
2006-06-15 12:49     ` Santi
2006-06-15 13:00       ` Alexander Litvinov [this message]
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=200606152000.43029.lan@academsoft.ru \
    --to=lan@academsoft.ru \
    --cc=git@vger.kernel.org \
    --cc=iler.ml@gmail.com \
    --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).