From: "B.G. Bruce" <bgb@nt-nv.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: tools/vnet build issues and a patch to fix part
Date: Wed, 09 Feb 2005 12:02:07 -0400 [thread overview]
Message-ID: <1107964927.9884.223.camel@master.vms.security> (raw)
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
Being that driver domains/xend are partially broken for me I thought I'd
take a run at vnet to accomplish something close to what I desire. Is
anyone else out there running vnet? If so, how stable have you found
it?
My findings to date are as follows:
1) building of gc is broken (at least for me). I needed the attached
patch to get things working properly.
PATCH tools_vnet_Makefile.gc-6.3.patch - Signed off by: bgb@nt-nv.com
2) The actual vnet-module driver is failing to build with the following
errors:
________________________________________________________________________
In file included from vnetd.h:22,
from vcache.c:39:
../vnet-module/if_varp.h:39: warning: declaration does not declare
anything
In file included from vcache.c:39:
vnetd.h:40: warning: declaration does not declare anything
vcache.c: In function `varp_send':
vcache.c:105: error: structure has no member named `id'
vcache.c:106: error: structure has no member named `opcode'
vcache.c: In function `vcache_forward_varp':
vcache.c:506: error: structure has no member named `opcode'
vcache.c: In function `vcache_handle_message':
vcache.c:614: error: structure has no member named `opcode'
make[1]: *** [vcache.o] Error 1
make[1]: Leaving directory `/usr/src/bk/xen/tools/vnet/vnetd'
make: *** [vnetd] Error 2
_________________________________________________________________
Does anyone have an idea as to what opcode and id should be?
B.
[-- Attachment #2: tools_vnet_Makfiel.gc-6.3.patch --]
[-- Type: text/x-patch, Size: 522 bytes --]
diff -ruN xen-2.0-testing.bk/tools/vnet/Makefile xen/tools/vnet/Makefile
--- xen-2.0-testing.bk/tools/vnet/Makefile 2005-01-31 20:38:33.000000000 -0400
+++ xen/tools/vnet/Makefile 2005-02-09 11:28:48.132468424 -0400
@@ -20,10 +20,8 @@
tar xfz gc.tar.gz
ln -sf gc?.? gc
-gc/Makefile:
- (cd gc && ./configure --prefix=`pwd`/install)
-
gc-install: gc gc/Makefile
+ (cd gc && make test && ./configure --prefix=`pwd`/install)
make -C gc
make -C gc install
next reply other threads:[~2005-02-09 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 16:02 B.G. Bruce [this message]
2005-02-10 10:18 ` tools/vnet build issues and a patch to fix part Mike Wray
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 16:34 Ian Pratt
2005-02-09 17:15 ` B.G. Bruce
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=1107964927.9884.223.camel@master.vms.security \
--to=bgb@nt-nv.com \
--cc=xen-devel@lists.sourceforge.net \
/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.