All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Colp <Patrick.Colp@citrix.com>
To: Michael David Crawford <mdc@prgmr.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: 3.4.0 wants to download Linux despite its presence
Date: Fri, 22 May 2009 10:19:00 +0100	[thread overview]
Message-ID: <4A166E04.8060901@citrix.com> (raw)
In-Reply-To: <4A166C36.1010204@prgmr.com>

Michael David Crawford wrote:
> Patrick Colp wrote:
>> Doing make xen and make tools should be just fine (I do this regularly, 
>> as I don't want or need Linux to be constantly rebuilt and reinstalled 
>> when I'm only changing things to Xen and/or tools).
> 
> I don't know for sure, but I have the theory that "make world" will 
> build things that "make xen" and "make tools" don't, which will then 
> persist in being installed when later tools builds miss some things.

Hmm... I don't know if I've ever used "make world", actually. If I want to 
build everything, I just do "make" (it seems the difference is that world 
will do a clean and kdelete first).

The only difference I can see between using world vs xen and tools is that 
world also builds the stubdom (which can be done separately with "make 
stubdom").

So perhaps the thing to do if you want stubdom support too is to do:

sudo make install-xen
sudo make install-tools
sudo make install-stubdom


>> Did you install them after building (make install-xen and make 
>> install-tools)? I think you need to be sudo for it to install properly.
> 
> I think I tried those just a couple times, but killed them when they 
> started to build the Linux kernel again.

I don't think they should do that... but maybe they need to build the linux 
kernel once. I'm not sure, since I did build and install the linux kernel 
(but only once, ever after I just need to do xen and tools).


> I have a "make world" going right now, and will do a "make install" when 
> that's done.  I decided to just let it build Linux, just so I can be 
> certain everything else builds.

Yes, this certainly seems like the safe thing to do.


Patrick

  reply	other threads:[~2009-05-22  9:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 12:46 3.4.0 wants to download Linux despite its presence Michael David Crawford
2009-05-20 14:57 ` Ian Jackson
2009-05-20 15:14   ` Keir Fraser
2009-05-20 21:12     ` Jeremy Fitzhardinge
2009-05-21  3:27       ` Keir Fraser
2009-05-22  8:52   ` Michael David Crawford
2009-05-22  8:57     ` Patrick Colp
2009-05-22  9:11       ` Michael David Crawford
2009-05-22  9:19         ` Patrick Colp [this message]
2009-05-22  9:40           ` Michael David Crawford
2009-05-22  9:36         ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]

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=4A166E04.8060901@citrix.com \
    --to=patrick.colp@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=mdc@prgmr.com \
    --cc=xen-devel@lists.xensource.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 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.