From: "Yakov Lerner" <iler.ml@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] auto-detect changed $prefix in Makefile and properly rebuild to avoid broken install
Date: Wed, 14 Jun 2006 23:30:56 +0300 [thread overview]
Message-ID: <f36b08ee0606141330l28330d79hab1aec5c741188c7@mail.gmail.com> (raw)
In-Reply-To: <7vver3cxlw.fsf@assigned-by-dhcp.cox.net>
On 6/14/06, Junio C Hamano <junkio@cox.net> wrote:
> Yakov Lerner <iler.ml@gmail.com> writes:
>
> > 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.
> >
> > Signed-off-by: Yakov Lerner <iler.ml@gmail.com>
>
> I do not mind this per se, and probably even agree that this is
> an improvement compared to the current state of affairs, but a few
> points:
>
> - please make sure you clean that state file in "make clean";
done
> - we may want to make the state file a bit more visible (IOW, I
> somewhat do mind the name being dot-git-dot-prefix).
I renamed .git.prefix to GIT-PREFIX. Is this ok.
> - we might want to later (or at the same time as this patch)
> do "consistent set of compilation flags" (e.g. run early
> part of compilation with openssl SHA-1 implementation,
> interrupt it and build and link the rest with mozilla SHA-1
> implementation -- then you will get a nonsense binary without
> linker errors). It might make sense to prepare this
> mechanism so we could reuse it for that purpose.
Do you think two separate GIT-PREFIX and GIT-BUILD-FLAGS are needed,
or just once GIT-BUILD-FLAGS will do, which will include
prefixes (as passed with -D... to cc) ?
I think single GIT-BUILD-FLAGS
is enough, which will cover prefixes, too. Is this OK ?
BTW, I think it's useful to add Makefile itself as prerequisite for all *.o,
so change in Makefile will cause recompilations. Shall I include this
into this patch, too ?
Yakov
next prev parent reply other threads:[~2006-06-14 20:31 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 [this message]
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
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=f36b08ee0606141330l28330d79hab1aec5c741188c7@mail.gmail.com \
--to=iler.ml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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;
as well as URLs for NNTP newsgroup(s).