From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@li>
Subject: Re: [PATCH] Remus breaks the build
Date: Fri, 13 Aug 2010 14:14:13 -0700 [thread overview]
Message-ID: <4C65B5A5.8020202@goop.org> (raw)
In-Reply-To: <20100813194217.GA6981@kremvax.cs.ubc.ca>
On 08/13/2010 12:42 PM, Brendan Cully wrote:
> I assume you're talking about this snippet of tools/remus/kmod/Makefile:
>
> $(MAKE) -C $(KERNELDIR) SUBDIRS=`pwd` modules
>
> which expects to find a Makefile in $KERNELDIR but does the actual
> building in place, in the tools/remus/kmod directory (unless the
> kernel build system has changed recently?). I thought this was a
> pretty standard way to build out-of-tree kernel modules.
I don't ever build the kernel out of the Xen tree. In general, it
assumes the kernel tree has already been configured and built, which may
not be true if you're doing a parallel build, or if you're building the
Xen tree piecewise.
> I'm not sure why this is causing you problems (is it?), but if you're
> willing to carry sch_queue in the pvops tree, I'd be happy to drop
> tools/remus/kmod in the unstable tree.
Yes, I'm happy to include it. Do you have a git reference I can merge from?
J
next prev parent reply other threads:[~2010-08-13 21:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 0:38 [PATCH] Remus breaks the build Jeremy Fitzhardinge
2010-08-13 10:38 ` Ian Campbell
2010-08-13 11:55 ` Stefano Stabellini
2010-08-13 12:52 ` Ian Jackson
2010-08-13 19:44 ` Brendan Cully
2010-08-18 20:09 ` Brendan Cully
2010-08-13 19:42 ` Brendan Cully
2010-08-13 21:14 ` Jeremy Fitzhardinge [this message]
2010-08-14 4:25 ` Dulloor
2010-08-17 17:38 ` Brendan Cully
2010-08-18 13:40 ` Ian Jackson
2010-08-18 17:58 ` Brendan Cully
2010-08-19 14:38 ` Ian Jackson
2010-08-18 20:26 ` Brendan Cully
2010-08-18 20:34 ` Jed Smith
2010-08-18 20:39 ` Brendan Cully
2010-08-18 23:54 ` Jeremy Fitzhardinge
2010-08-19 0:03 ` Brendan Cully
2010-08-19 6:03 ` Pasi Kärkkäinen
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=4C65B5A5.8020202@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Xen-devel@li \
--cc=stefano.stabellini@eu.citrix.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.