From: Robin van Leeuwen <rvl@rldsoftware.nl>
To: xen-devel@lists.xensource.com
Subject: Compile problems shadow.c after hg pull -u
Date: Thu, 15 Dec 2005 14:29:52 +0100 [thread overview]
Message-ID: <43A16FD0.2000704@rldsoftware.nl> (raw)
After my last hg pull -u
hg tip
changeset: 8369:dc8122d90670
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Wed Dec 14 19:47:16 2005 +0100
summary: Fix the issue when guest OS clear TS bit by mov to cr0
instead of
i got some strange errors in compiling
Xen. They where all located in the file
/usr/src/xen/xen-unstable.hg/xen/arch/x86/shadow.c
Anyway, i have limited C experience, but the was a lot of rules in it like
> <<<<<<< /tmp/shadow.c~base.2FTtb9
> need_flush |= resync_all(d, PGT_l2_shadow);
> =======
So everywhere wehere the was a <<<<<<<, i deleted until the ===========
and everywhere there was >>>>>>>> i left (removed >>>>>> and ========)
offcourse
my diff file before and after is attached, maybe can give some help....
seems so compile ok now (amd64, 64 bit mode)
kind regards, robin
next reply other threads:[~2005-12-15 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 13:29 Robin van Leeuwen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-15 13:31 Compile problems shadow.c after hg pull -u Robin van Leeuwen
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=43A16FD0.2000704@rldsoftware.nl \
--to=rvl@rldsoftware.nl \
--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.