From: jason <fearthepenguin@jasonandjessi.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: 3.0.3 without X
Date: Thu, 04 Jan 2007 08:54:42 -0600 [thread overview]
Message-ID: <459D1532.1060908@jasonandjessi.com> (raw)
Hello,
I have posted this to the users list, but haven't had much luck.
I've also used my best google-fu, which may be lacking, and searched the
archives.
I run Dom0 in a very bare bones enviroment that fits on a CF card. My
DomUs then use my harddrives and Dom0 is left only wih the task of
managing my DomUs. This has worked out really well for me using Xen
3.0HG-Unstable (old old old). I've tried to recently move to 3.0.3 and
a new dependency on X Windows seems to have popped up. I can't get my
compile to make it past the ioemu/vnc.c parts since I don't have
anything resembling X installed. Is their a way to compile 3.0.3
without the X dependency? I don't have any HVM hardware, so that's not
a concern for me and I've already tried to edit config/x86_32.mk.
Thanks!
/mnt/share/xen-3.0.3_0-src/tools/ioemu/vnc.c:50:27: X11/keysymdef.h: No
such file or directory
/mnt/share/xen-3.0.3_0-src/tools/ioemu/vnc.c: In function `do_key_event':
...blah blah blah...
/mnt/share/xen-3.0.3_0-src/tools/ioemu/vnc.c: In function
`protocol_client_msg':
/mnt/share/xen-3.0.3_0-src/tools/ioemu/vnc.c:1069: warning: unused
variable `now'
make[5]: *** [vnc.o] Error 1
--
Jason
The place where you made your stand never mattered,
only that you were there... and still on your feet
next reply other threads:[~2007-01-04 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 14:54 jason [this message]
2007-01-04 14:58 ` 3.0.3 without X ron minnich
2007-01-04 15:01 ` Keir Fraser
2007-01-04 15:32 ` Ewan Mellor
2007-01-04 17:57 ` ron minnich
2007-01-04 18:11 ` jason
2007-01-04 18:12 ` Mark Williamson
2007-01-04 22:31 ` Ewan Mellor
2007-01-05 9:31 ` Dependency checking - early was " Steve Kemp
2007-01-04 19:32 ` Anthony Liguori
2007-01-04 19:48 ` Ewan Mellor
2007-01-04 21:17 ` Anthony Liguori
2007-01-04 22:38 ` Ewan Mellor
2007-01-04 14:59 ` Keir Fraser
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=459D1532.1060908@jasonandjessi.com \
--to=fearthepenguin@jasonandjessi.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.