From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Nguyen Anh Quynh <aquynh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [patch] Make sure that we compile before installing
Date: Mon, 23 Jul 2007 12:15:58 +0300 [thread overview]
Message-ID: <46A471CE.3010004@qumranet.com> (raw)
In-Reply-To: <9cde8bff0707230212y15855939q32c61d9a4cffc4c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Nguyen Anh Quynh wrote:
> On 7/23/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>> Nguyen Anh Quynh wrote:
>> > This patch makes "install" compile code, and "install-rpm" package
>> rpms.
>>
>> 'install' and 'install-rpm' are typically run as root, and we don't want
>> to compile as root.
>
> Is it because of security reason, or something else?
>
Just standard practice. For example, my home directory is nfs mounted,
so I can't compile as root. Since I sometimes test before committing,
I'd like to keep the ability to compile.
> I want this patch because without it, sometimes I install without
> recompiling. As a result, the old binary is installed, and I dont
> notice that I dont run the code with new change. That really confuses,
> and even took me a while to figure out what actually happend.
Run 'make && make install' (or a script that does that) instead.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-07-23 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 8:49 [patch] Make sure that we compile before installing Nguyen Anh Quynh
[not found] ` <9cde8bff0707230149x5cf686cbh45f68ce30a82c87f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-23 9:05 ` Avi Kivity
[not found] ` <46A46F3F.1020802-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-23 9:12 ` Nguyen Anh Quynh
[not found] ` <9cde8bff0707230212y15855939q32c61d9a4cffc4c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-23 9:15 ` Avi Kivity [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=46A471CE.3010004@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=aquynh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.