From: Gerd Hoffmann <kraxel@suse.de>
To: Ian Campbell <Ian.Campbell@XenSource.com>
Cc: Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: BUG: make O= broken
Date: Thu, 07 Dec 2006 12:00:32 +0100 [thread overview]
Message-ID: <4577F450.6010804@suse.de> (raw)
In-Reply-To: <1165487554.9694.140.camel@localhost.localdomain>
Ian Campbell wrote:
> On Thu, 2006-12-07 at 11:19 +0100, Gerd Hoffmann wrote:
>> Building xenlinux kernels with separate source/build trees (aka "make
>> O=/path/to/build/tree") doesn't work.
>
> I build that way all the time, what specifically is broken?
Sorry, was something different.
I've tried to turn the sparse tree into a big patch (is there an easy
way to do this btw?). Documentation/dontdiff excludes too much giving
me a incomplete xenlinux tree, which in turn generated build errors
looking much like it takes the wrong (native) include files. I've seen
that in the past with O=, so I blamed it first ...
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
next prev parent reply other threads:[~2006-12-07 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 10:19 BUG: make O= broken Gerd Hoffmann
2006-12-07 10:32 ` Ian Campbell
2006-12-07 11:00 ` Gerd Hoffmann [this message]
2006-12-07 11:08 ` Ian Campbell
2006-12-07 11:18 ` Gerd Hoffmann
2006-12-07 13:18 ` 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=4577F450.6010804@suse.de \
--to=kraxel@suse.de \
--cc=Ian.Campbell@XenSource.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.