Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Matthias Lederhofer <matled@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: disable the compile-flags-changed check
Date: Sat, 15 Jul 2006 14:48:18 -0700	[thread overview]
Message-ID: <7vbqrqmtel.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <E1G1qAS-0005gv-P7@moooo.ath.cx> (Matthias Lederhofer's message of "Sat, 15 Jul 2006 21:51:12 +0200")

Matthias Lederhofer <matled@gmx.net> writes:

> Junio C Hamano <junkio@cox.net> wrote:
>> Matthias Lederhofer <matled@gmx.net> writes:
>> 
>> > Is there any way to disable the "the compile flags have changed,
>> > recompile everything" check?  I want to built with another prefix than
>> > installing to create a tarball I copy to other machines.  Is there any
>> > way to do this?
>> 
>> Perhaps
>> 
>> 	DESTDIR=/var/tmp/ make prefix=/usr install
>> 
>> is what you are looking for?
>
> Thanks, this works.

By the way, in older days before binary distributions have
become _the_ way for the end users to get programs, "install
into a saparate place for tarring up" needed to be custom job
per package, because Makefiles of many packages were not set up
to easily allow it (like DESTDIR= stuff).  These days, allowing
it is almost a requirement in order to make binary distros'
lives easier, so if a program is packaged for some binary
distros (say, RPM or deb), often the easiest way to figure out
the answer to your question is to see how they build their
packages out of the source.

      reply	other threads:[~2006-07-15 21:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14  5:47 disable the compile-flags-changed check Matthias Lederhofer
2006-07-14  6:06 ` Junio C Hamano
2006-07-15 19:51   ` Matthias Lederhofer
2006-07-15 21:48     ` Junio C Hamano [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=7vbqrqmtel.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=matled@gmx.net \
    /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