All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: stubdom questions
Date: Tue, 9 Nov 2010 21:48:48 +0100	[thread overview]
Message-ID: <20101109204848.GN3448@const> (raw)
In-Reply-To: <4CD9341702000078000211AD@vpn.id2.novell.com>

Jan Beulich, le Tue 09 Nov 2010 10:44:23 +0000, a écrit :
> - the build produces dozens of compiler warnings quite a few of which
> don't look benign at all?

On which parts? I guess updating them might fix these warnings, and if
not, issues should rather be reported upstream.

> - can't be built with a read-only and/or symlinked source tree?

I've never tried, actually.

> Also, what's the point of the install-stubdom dependency on
> install-tools? Shouldn't the individual components' builds be
> independent of one another?

I don't know why, but it's

changeset:   21760:84719437205c
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Fri Jul 09 12:22:52 2010 +0100
summary:     Makefile: Serialise stubdom build after tools

Samuel

  parent reply	other threads:[~2010-11-09 20:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 10:44 stubdom questions Jan Beulich
2010-11-09 17:00 ` Ian Jackson
2010-11-09 17:05   ` Jan Beulich
2010-11-09 17:31     ` Stefano Stabellini
2010-11-10 10:01   ` Jan Beulich
2010-11-10 12:08     ` Gianni Tedesco
2010-11-10 13:55     ` Ian Jackson
2010-11-09 20:48 ` Samuel Thibault [this message]
2010-11-10  9:58   ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2008-09-09  4:43 Lu, Guanqun
2008-02-19 11:39 Zhai, Edwin
2008-02-25 11:56 ` Samuel Thibault
2008-02-27  2:05   ` Zhai, Edwin
2008-02-27 11:12     ` Samuel Thibault

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=20101109204848.GN3448@const \
    --to=samuel.thibault@ens-lyon.org \
    --cc=JBeulich@novell.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.