qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] [Qemu-devel] [PATCH v2 0/2] s390x/kvm: Properly detect pa


From: David Hildenbrand
Subject: Re: [Qemu-ppc] [Qemu-devel] [PATCH v2 0/2] s390x/kvm: Properly detect page size of initial memory
Date: Thu, 28 Mar 2019 13:53:21 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0

On 28.03.19 13:38, address@hidden wrote:
> Patchew URL: https://patchew.org/QEMU/address@hidden/
> 
> 
> 
> Hi,
> 
> This series failed the address@hidden build test. Please find the testing 
> commands and
> their output below. If you have Docker installed, you can probably reproduce 
> it
> locally.
> 
> === TEST SCRIPT BEGIN ===
> #!/bin/bash
> time make address@hidden SHOW_ENV=1 J=14 NETWORK=1
> === TEST SCRIPT END ===
> 
>   CC      aarch64-softmmu/gdbstub-xml.o
>   CC      aarch64-softmmu/trace/generated-helpers.o
>   CC      aarch64-softmmu/target/arm/translate-sve.o
> /tmp/qemu-test/src/exec.c:1776:6: error: no previous prototype for 
> 'qemu_getminrampagesize' [-Werror=missing-prototypes]
>  long qemu_getminrampagesize(void)
>       ^~~~~~~~~~~~~~~~~~~~~~
> /tmp/qemu-test/src/exec.c:1780:6: error: no previous prototype for 
> 'qemu_getmaxrampagesize' [-Werror=missing-prototypes]
>  long qemu_getmaxrampagesize(void)
>       ^~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
> make[1]: *** [/tmp/qemu-test/src/rules.mak:69: exec.o] Error 1
> make: *** [Makefile:449: subdir-x86_64-softmmu] Error 2
> make: *** Waiting for unfinished jobs....
> /tmp/qemu-test/src/exec.c:1776:6: error: no previous prototype for 
> 'qemu_getminrampagesize' [-Werror=missing-prototypes]
>  long qemu_getminrampagesize(void)
>       ^~~~~~~~~~~~~~~~~~~~~~
> /tmp/qemu-test/src/exec.c:1780:6: error: no previous prototype for 
> 'qemu_getmaxrampagesize' [-Werror=missing-prototypes]
>  long qemu_getmaxrampagesize(void)
>       ^~~~~~~~~~~~~~~~~~~~~~

Yes, missed to commit a change. But let's see first if this is the right
approach.


-- 

Thanks,

David / dhildenb



reply via email to

[Prev in Thread] Current Thread [Next in Thread]