From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2186151 ] qemu/qemu-kvm.c:356 SegmentCache breaks kvm-ia64 building
Date: Mon, 8 Dec 2008 02:22:16 +0000 [thread overview]
Message-ID: <E1L9VlI-0006iQ-Rk@49zxpd1.ch3.sourceforge.com> (raw)
Bugs item #2186151, was opened at 2008-10-22 05:46
Message generated for change (Comment added) made by sf-robot
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2186151&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: intel
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Zhang Jingke (zhangjingke)
Assigned to: Nobody/Anonymous (nobody)
Summary: qemu/qemu-kvm.c:356 SegmentCache breaks kvm-ia64 building
Initial Comment:
We found recently kvm-ia64 building was broken by the error in qemu/qemu-kvm.c. Those codes should be special for x86 side.
Detail error info are:
==================
/home/build/kvm-build/kvm-userspace/qemu/qemu-kvm.c:356: error:
SegmentCache undeclared (first use in this function)
/home/build/kvm-build/kvm-userspace/qemu/qemu-kvm.c:356: error: (Each
undeclared identifier is reported only once
/home/build/kvm-build/kvm-userspace/qemu/qemu-kvm.c:356: error: for each
function it appears in.)
/home/build/kvm-build/kvm-userspace/qemu/qemu-kvm.c:356: error: expected
; before cs
/home/build/kvm-build/kvm-userspace/qemu/qemu-kvm.c:362: error:
CPUIA64State has no member named segs
/home/build/kvm-build/kvm-userspace/qemu/qemu-kvm.c:362: error: R_CS
undeclared (first use in this function)
/home/build/kvm-build/kvm-userspace/qemu/qemu-kvm.c:362: error: cs
undeclared (first use in this function)
make[2]: *** [qemu-kvm.o] Error 1
make[2]: Leaving directory
`/home/build/kvm-build/kvm-userspace/qemu/ia64-softmmu'
make[1]: *** [subdir-ia64-softmmu] Error 2
make[1]: Leaving directory `/home/build/kvm-build/kvm-userspace/qemu'
make: *** [qemu] Error 2
----------------------------------------------------------------------
>Comment By: SourceForge Robot (sf-robot)
Date: 2008-12-08 02:22
Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
----------------------------------------------------------------------
Comment By: Avi Kivity (avik)
Date: 2008-11-23 19:10
Message:
Should be fixed now.
----------------------------------------------------------------------
Comment By: Zhang Jingke (zhangjingke)
Date: 2008-10-22 05:53
Message:
Add some more information:
Userspace Commit: 2a433458f6f7ba93328bfd17c9b678b9180daf94
Kernel-ia64 Commit:d0ea17370a66375634986788cff333ab9610ed9f
Host Kernel Version: 2.6.27-rc9
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2186151&group_id=180599
reply other threads:[~2008-12-08 2:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1L9VlI-0006iQ-Rk@49zxpd1.ch3.sourceforge.com \
--to=noreply@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.