From: "Christoph Egger" <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Subject: Re: Building broken with CS 13282
Date: Mon, 8 Jan 2007 15:40:32 +0100 [thread overview]
Message-ID: <200701081540.32377.Christoph.Egger@amd.com> (raw)
In-Reply-To: <20070108143057.GA537@totally.trollied.org.uk>
On Monday 08 January 2007 15:30, John Levon wrote:
> On Mon, Jan 08, 2007 at 02:13:32PM +0000, John Levon wrote:
> > For one thing I can't see a dependency such that compat/xen.[ch] will be
> > built before compat/acm.[ch], and there don't seem to be gcc-generated
> > deps either ?
>
> And even if I do:
>
> compat/xen.c:30:24: xen-compat.h: No such file or directory
> compat/xen.c:33:26: arch-x86/xen.h: No such file or directory
>
> Ading -I public helps until it tries to make 'archa64.h', which looks
> awfully like a mangled arch-ia64.h, though I don't follow how that's
> happened.
Perhaps this has to do with different sed implementations.
OpenBSD sed doesn't support alternatives as used in this
snippet from xen/include/Makefile:
sed -e 's,__InClUdE__,#include,' \
-e 's,"xen-compat.h",<public/xen-compat.h>,' \
-e 's,\(struct\|union\|enum\)[[:space:]]\+\(xen_\?\)\?
\([[:alpha:]_]\),\1 compat_\3,g' \
So that's at least one reason for the build failure on OpenBSD.
On Linux with GNU sed, it builds for me.
Christoph
next prev parent reply other threads:[~2007-01-08 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 10:49 Building broken with CS 13282 Christoph Egger
2007-01-08 11:07 ` Keir Fraser
2007-01-08 12:24 ` John Levon
2007-01-08 13:19 ` Keir Fraser
2007-01-08 14:13 ` John Levon
2007-01-08 14:30 ` John Levon
2007-01-08 14:40 ` Christoph Egger [this message]
2007-01-08 14:50 ` John Levon
2007-01-08 16:17 ` Keir Fraser
2007-01-08 17:26 ` John Levon
2007-01-08 18:48 ` Keir Fraser
2007-01-08 18:52 ` John Levon
2007-01-09 8:25 ` Jan Beulich
2007-01-08 12:20 ` Yu, Ping Y
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=200701081540.32377.Christoph.Egger@amd.com \
--to=christoph.egger@amd.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.