All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Edwards <edwardsg@sgi.com>
To: dan.magenheimer@hp.com
Cc: xen-devel@lists.sourceforge.net
Subject: building current xen/ia64
Date: Fri, 11 Feb 2005 09:29:41 -0600	[thread overview]
Message-ID: <20050211152941.GA30564@sgi.com> (raw)

Dan,

Does ftp://ftp.hpl.hp.com/pub/xen-ia64/ still contain the most current
xen/ia64 code?  It's getting the following compile error on an ia64 SLES
box (gcc-3.3.3):

make -C arch/ia64
make[1]: Entering directory `/data/lwork/attica2/edwardsg/xen-ia64/xen-2.0/xen/arch/ia64'
cc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -O2 -iwithprefix include -Wall -DMONITOR_BASE=0xFC500000 -fomit-frame-pointer -I/data/lwork/attica2/edwardsg/xen-ia64/xen-2.0/xen/include -D__KERNEL__ -I/data/lwork/attica2/edwardsg/xen-ia64/xen-2.0/xen/include/asm-ia64 -Wno-pointer-arith -Wredundant-decls -DIA64 -DXEN -DLINUX_2_6 -ffixed-r13 -mfixed-range=f12-f15,f32-f127 -w -g -DNDEBUG -c vcpu.c -o vcpu.o
vcpu.c: In function `vcpu_get_ipsr_int_state':
vcpu.c:281: error: union has no member named `be'
vcpu.c:281: error: union has no member named `be'
vcpu.c:282: error: union has no member named `pp'
vcpu.c:282: error: union has no member named `pp'
vcpu.c:283: error: union has no member named `ic'
vcpu.c:284: error: union has no member named `i'
vcpu.c:285: error: union has no member named `bn'
vcpu.c:286: error: union has no member named `dt'
vcpu.c:286: error: union has no member named `it'
vcpu.c:286: error: union has no member named `rt'
vcpu.c:287: error: union has no member named `cpl'
vcpu.c:287: error: union has no member named `cpl'
vcpu.c: In function `vcpu_rfi':
vcpu.c:1003: error: union has no member named `cpl'
vcpu.c:1003: error: union has no member named `cpl'
vcpu.c:1004: error: union has no member named `i'
vcpu.c:1005: error: union has no member named `i'
vcpu.c:1006: error: union has no member named `ic'
vcpu.c:1007: error: union has no member named `dt'
vcpu.c:1007: error: union has no member named `rt'
vcpu.c:1007: error: union has no member named `it'
vcpu.c:1009: error: union has no member named `ic'
vcpu.c:1009: error: union has no member named `i'
vcpu.c:1010: error: union has no member named `dt'
vcpu.c:1010: error: union has no member named `rt'
vcpu.c:1010: error: union has no member named `it'
vcpu.c:1011: error: union has no member named `bn'
vcpu.c:1013: error: union has no member named `be'
make[1]: *** [vcpu.o] Error 1

I ran build-xenia64-xen.2.0.1 for setting up and patching the tree, but
perhaps I missed a step.

I switched PSR to typedef struct ia64_psr as a quick sanity check, then
if barfed about the psr.i64 assignment (i64 isn't in struct ia64_psr).
So I strongly suspect I'm missing a patch, or the tree wasn't patched
correctly.  A kick in the right direction would be appreciated.

Greg


-------------------------------------------------------
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-11 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 15:29 Greg Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-11 16:35 building current xen/ia64 Magenheimer, Dan (HP Labs Fort Collins)

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=20050211152941.GA30564@sgi.com \
    --to=edwardsg@sgi.com \
    --cc=dan.magenheimer@hp.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.