All of lore.kernel.org
 help / color / mirror / Atom feed
From: "B.G. Bruce" <bgb@nt-nv.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>,
	Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Subject: RE: tools/vnet build issues and a patch to fix part
Date: Wed, 09 Feb 2005 13:15:29 -0400	[thread overview]
Message-ID: <1107969329.9884.264.camel@master.vms.security> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D123805@liverpoolst.ad.cl.cam.ac.uk>

On Wed, 2005-02-09 at 12:34, Ian Pratt wrote:

> You don't half like living on the bleeding edge ;-)

Something about frying pans and a fire comes to mind.  :-) 

> I'm not aware of anyone outside HP that uses vnets regularly, but
> they're a cool thing that we want to maintain.
> 
> I suspect that the current breakage is because the code was written for
> 2.6.7, and there have been updates since. Syncing up probably isn't very
> hard. Perhaps a volunteer will step forward....

from what I have seen so far, it probably got more to do with how
VnetMsgHdr is being used in VarpHdr (both in vnet-modules/if_varp.h) and
things that earlier versions of gcc allowed that gcc 3.3.5 doesn't.  At
least that's my initial thoughts. (gentoo-dev-sources-2.6.10-r6) in case
you were wondering .... 

Now if I was REALLY bleeding edge I would be doing the initial setup
with gentoo-hardened (2.6.x) (grsecurity/ssp/pie) on uClibc and
gcc-3.4.x.

> Ian 
>  
> > 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.
> > 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-09 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 16:34 tools/vnet build issues and a patch to fix part Ian Pratt
2005-02-09 17:15 ` B.G. Bruce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-09 16:02 B.G. Bruce
2005-02-10 10:18 ` Mike Wray

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=1107969329.9884.264.camel@master.vms.security \
    --to=bgb@nt-nv.com \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.