public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Muli Ben-Yehuda <muli-7z/5BgaJwgfQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [kvm-commits] kvm: revert r4386 (rev 4422)
Date: Wed, 14 Feb 2007 15:15:37 +0200	[thread overview]
Message-ID: <45D30B79.6080807@qumranet.com> (raw)
In-Reply-To: <20070214083039.GE461-k73YwwB0fHlWk0Htik3J/w@public.gmane.org>

Muli Ben-Yehuda wrote:
> On Wed, Feb 14, 2007 at 10:25:46AM +0200, Avi Kivity wrote:
>   
>> Muli Ben-Yehuda wrote:
>>     
>>> On Wed, Feb 14, 2007 at 09:57:13AM +0200, Avi Kivity wrote:
>>>  
>>>       
>>>> kvm: revert r4386
>>>>
>>>> causes breakage, as well as using evil '?=' assignment.
>>>>    
>>>>         
>>> *sigh*, this breaks --kerneldir.
>>>
>>> The patch I resent early this morning does the right thing.
>>>       
>> Well, --kerneldir should be fixed without ?= and with testing.
>>     
>
> What's wrong with '?='?
>   

It allows environment variables to affect the compilation.


> Are we requiring running `configure' in the top level before running
> 'make' in kernel/? 

For now, yes.  If it's desired to have kernel/ as a standalone 
directory, it should have its own ./configure (called from the top-level 
./configure for a full build).

> if yes, getting rid of the KERNELDIR assignment in
> kernel/Makefile is trivial, if not, '?=' expresses the semantics
> exactly - if KERNELDIR is already set, use that, if not set it to the
> default.
>   

Maybe.  I'm just not up to testing 3 options x a zillion distros.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2007-02-14 13:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070214075713.2D6DC250354@il.qumranet.com>
     [not found] ` <20070214075713.2D6DC250354-LjA0eNSCdXrQnzwC+xcbyw@public.gmane.org>
2007-02-14  8:06   ` [kvm-commits] kvm: revert r4386 (rev 4422) Muli Ben-Yehuda
     [not found]     ` <20070214080623.GD461-k73YwwB0fHlWk0Htik3J/w@public.gmane.org>
2007-02-14  8:25       ` Avi Kivity
     [not found]         ` <45D2C78A.4060203-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-14  8:30           ` Muli Ben-Yehuda
     [not found]             ` <20070214083039.GE461-k73YwwB0fHlWk0Htik3J/w@public.gmane.org>
2007-02-14 13:15               ` Avi Kivity [this message]
     [not found]                 ` <45D30B79.6080807-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-14 13:31                   ` Laurent Vivier
2007-02-14 17:50                   ` Muli Ben-Yehuda

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=45D30B79.6080807@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=muli-7z/5BgaJwgfQT0dZR+AlfA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox