[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PULL 0/8] s390x patches for 2.2
From: |
Cornelia Huck |
Subject: |
Re: [Qemu-devel] [PULL 0/8] s390x patches for 2.2 |
Date: |
Thu, 9 Oct 2014 19:18:02 +0200 |
On Thu, 9 Oct 2014 17:22:27 +0100
Peter Maydell <address@hidden> wrote:
> On 9 October 2014 14:35, Cornelia Huck <address@hidden> wrote:
> > The following changes since commit b6011bd8a57c1eda81a857d21adeb9b66e58b1b0:
> >
> > Merge remote-tracking branch
> > 'remotes/riku/tags/pull-linux-user-20141006-2' into staging (2014-10-07
> > 10:41:48 +0100)
> >
> > are available in the git repository at:
> >
> >
> > git://github.com/cohuck/qemu.git tags/s390x-20141009
> >
> > for you to fetch changes up to 2adf6bbb8ad7e53f602d10b2b30d22cd831f79a6:
> >
> > s390x/virtio-ccw: fix vhost-scsi intialization (2014-10-09 14:22:47 +0200)
> >
> > ----------------------------------------------------------------
> > various s390x updates:
> > - cpu state handling in qemu and migration
> > - vhost-scsi-ccw bugfix
>
> Hi. I'm afraid this fails to link the linux-user target:
>
> LINK s390x-linux-user/qemu-s390x
> target-s390x/cpu.o:(.data+0xbc): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0xec): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x11c): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x14c): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x17c): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x1ac): more undefined references to
> `vmstate_info_uint64' follow
> target-s390x/cpu.o:(.data+0x47c): undefined reference to `vmstate_info_uint32'
> target-s390x/cpu.o:(.data+0x4ac): undefined reference to `vmstate_info_uint32'
> target-s390x/cpu.o:(.data+0x4dc): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x50c): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x53c): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x56c): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x59c): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x5cc): more undefined references to
> `vmstate_info_uint64' follow
> target-s390x/cpu.o:(.data+0x62c): undefined reference to `vmstate_info_uint32'
> target-s390x/cpu.o:(.data+0x65c): undefined reference to `vmstate_info_uint64'
> target-s390x/cpu.o:(.data+0x68c): undefined reference to `vmstate_info_uint8'
> collect2: error: ld returned 1 exit status
*scratches head*
Weird, s390x-linux-user seems to build for me on s390x (just tried
again).
I guess you build on !s390x, though :) I'll look into this.
- [Qemu-devel] [PULL 4/8] s390x/kvm: propagate s390 cpu state to kvm, (continued)
- [Qemu-devel] [PULL 4/8] s390x/kvm: propagate s390 cpu state to kvm, Cornelia Huck, 2014/10/09
- [Qemu-devel] [PULL 1/8] linux-headers: update to 3.17-rc7, Cornelia Huck, 2014/10/09
- [Qemu-devel] [PULL 5/8] s390x/kvm: reuse kvm_s390_reset_vcpu() to get rid of ifdefs, Cornelia Huck, 2014/10/09
- [Qemu-devel] [PULL 6/8] s390x/kvm: synchronize the cpu state after SIGP (INITIAL) CPU RESET, Cornelia Huck, 2014/10/09
- [Qemu-devel] [PULL 7/8] s390x/migration: migrate CPU state, Cornelia Huck, 2014/10/09
- [Qemu-devel] [PULL 8/8] s390x/virtio-ccw: fix vhost-scsi intialization, Cornelia Huck, 2014/10/09
- Re: [Qemu-devel] [PULL 0/8] s390x patches for 2.2, Peter Maydell, 2014/10/09
- Re: [Qemu-devel] [PULL 0/8] s390x patches for 2.2,
Cornelia Huck <=