From: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> To: Jon Doron <arilou@gmail.com> Cc: "Thomas Huth" <thuth@redhat.com>, "Philippe Mathieu-Daudé" <philmd@redhat.com>, "QEMU Developers" <qemu-devel@nongnu.org>, "Paolo Bonzini" <pbonzini@redhat.com>, "Bug 1885247" <1885247@bugs.launchpad.net>, "Alex Bennée" <alex.bennee@linaro.org> Subject: Re: [Bug 1885247] [NEW] Build error in Intel 32-bit hosts Date: Fri, 26 Jun 2020 13:20:08 +0200 [thread overview] Message-ID: <CAHiYmc7SrqDZQzEdfM7NKt=vPjmXACQF+C45R76yNEgq1VQJxw@mail.gmail.com> (raw) In-Reply-To: <CAP7QCoiuc3ZYXowBi6TahYEoxM3fiUQAwfo=pSUZeG5yOGTY9Q@mail.gmail.com> пет, 26. јун 2020. у 12:54 Jon Doron <arilou@gmail.com> је написао/ла: > > Is there a container I can download which has your build environment? > Hello, Jon. I don't know about the container, but, as Peter noted, the following (non-beautiful) diff fixes the build problem on the real host: diff --git a/hw/hyperv/vmbus.c b/hw/hyperv/vmbus.c index f371240176..9220f7b529 100644 --- a/hw/hyperv/vmbus.c +++ b/hw/hyperv/vmbus.c @@ -383,7 +383,8 @@ static ssize_t gpadl_iter_io(GpadlIter *iter, void *buf, uint32_t len) } } - p = (void *)(((uintptr_t)iter->map & TARGET_PAGE_MASK) | off_in_page); + p = (void *)(uintptr_t)(((uintptr_t)iter->map & TARGET_PAGE_MASK) | + off_in_page); if (iter->dir == DMA_DIRECTION_FROM_DEVICE) { memcpy(p, buf, cplen); } else { Not sure if this is an optimal/most-elegant solution though. Warmly, Aleksandar > On Fri, Jun 26, 2020 at 12:27 PM Philippe Mathieu-Daudé > <philmd@redhat.com> wrote: > > > > On 6/26/20 11:20 AM, Thomas Huth wrote: > > > On 26/06/2020 11.13, Philippe Mathieu-Daudé wrote: > > >> On 6/26/20 9:37 AM, Aleksandar Markovic wrote: > > >>> пет, 26. јун 2020. у 09:11 Aleksandar Markovic > > >>> <1885247@bugs.launchpad.net> је написао/ла: > > >>>> > > >>>> Public bug reported: > > >>>> > > >>>> The code base is on master, checked out on Thursday June25th 2020, > > >>>> 0250c595c9d. The build procedure: > > >>>> > > >>>> $ mkdir build-gcc > > >>>> $ cd build-gcc > > >>>> $ ../configure > > >>>> $ make > > >>>> > > >>>> The build error message is: > > >>>> > > >>>> CC x86_64-softmmu/hw/hyperv/hyperv.o > > >>>> CC x86_64-softmmu/hw/hyperv/hyperv_testdev.o > > >>>> CC x86_64-softmmu/hw/hyperv/vmbus.o > > >>>> /home/rtrk/Build/qemu-master/hw/hyperv/vmbus.c: In function > > >>>> ‘gpadl_iter_io’: > > >>>> /home/rtrk/Build/qemu-master/hw/hyperv/vmbus.c:386:13: error: cast > > >>>> to pointer from integer of different size [-Werror=int-to-pointer-cast] > > >>>> p = (void *)(((uintptr_t)iter->map & TARGET_PAGE_MASK) | > > >>>> off_in_page); > > >>>> ^ > > >>>> cc1: all warnings being treated as errors > > >>>> make[1]: *** [/home/rtrk/Build/qemu-master/rules.mak:69: > > >>>> hw/hyperv/vmbus.o] Error 1 > > >>>> make: *** [Makefile:527: x86_64-softmmu/all] Error 2 > > >> > > >> FWIW there is no CI job covering x86 KVM on 32-bit host build. > > >> Should this be covered? I guess the problem is no CI services > > >> provide 32-bit x86... > > > > > > You can certainly provide either a container, or install the 32-bit > > > libraries in a 64-bit environment. Then run > > > > > > PKG_CONFIG_LIBDIR=... ./configure --extra-cflags=-m32 > > > > > > and it should be possible to build 32-bit binaries, too. > > > > > > Alternatively, we could add a cross-compilation job that builds with > > > i686-w64-mingw32 in 32-bit. > > > > Oh, this case is covered: > > https://app.shippable.com/github/qemu/qemu/runs/2437/2/console > > > > But this doesn't use KVM ;) > >
WARNING: multiple messages have this Message-ID (diff)
From: Aleksandar Markovic <1885247@bugs.launchpad.net> To: qemu-devel@nongnu.org Subject: Re: [Bug 1885247] [NEW] Build error in Intel 32-bit hosts Date: Fri, 26 Jun 2020 11:20:08 -0000 [thread overview] Message-ID: <CAHiYmc7SrqDZQzEdfM7NKt=vPjmXACQF+C45R76yNEgq1VQJxw@mail.gmail.com> (raw) Message-ID: <20200626112008.5uF4TVqvVXT8PqCfugMbElv7kwffl_tjsMJONyLvV7k@z> (raw) In-Reply-To: 159315507826.13901.17398620572438937429.malonedeb@wampee.canonical.com пет, 26. јун 2020. у 12:54 Jon Doron <arilou@gmail.com> је написао/ла: > > Is there a container I can download which has your build environment? > Hello, Jon. I don't know about the container, but, as Peter noted, the following (non-beautiful) diff fixes the build problem on the real host: diff --git a/hw/hyperv/vmbus.c b/hw/hyperv/vmbus.c index f371240176..9220f7b529 100644 --- a/hw/hyperv/vmbus.c +++ b/hw/hyperv/vmbus.c @@ -383,7 +383,8 @@ static ssize_t gpadl_iter_io(GpadlIter *iter, void *buf, uint32_t len) } } - p = (void *)(((uintptr_t)iter->map & TARGET_PAGE_MASK) | off_in_page); + p = (void *)(uintptr_t)(((uintptr_t)iter->map & TARGET_PAGE_MASK) | + off_in_page); if (iter->dir == DMA_DIRECTION_FROM_DEVICE) { memcpy(p, buf, cplen); } else { Not sure if this is an optimal/most-elegant solution though. Warmly, Aleksandar > On Fri, Jun 26, 2020 at 12:27 PM Philippe Mathieu-Daudé > <philmd@redhat.com> wrote: > > > > On 6/26/20 11:20 AM, Thomas Huth wrote: > > > On 26/06/2020 11.13, Philippe Mathieu-Daudé wrote: > > >> On 6/26/20 9:37 AM, Aleksandar Markovic wrote: > > >>> пет, 26. јун 2020. у 09:11 Aleksandar Markovic > > >>> <1885247@bugs.launchpad.net> је написао/ла: > > >>>> > > >>>> Public bug reported: > > >>>> > > >>>> The code base is on master, checked out on Thursday June25th 2020, > > >>>> 0250c595c9d. The build procedure: > > >>>> > > >>>> $ mkdir build-gcc > > >>>> $ cd build-gcc > > >>>> $ ../configure > > >>>> $ make > > >>>> > > >>>> The build error message is: > > >>>> > > >>>> CC x86_64-softmmu/hw/hyperv/hyperv.o > > >>>> CC x86_64-softmmu/hw/hyperv/hyperv_testdev.o > > >>>> CC x86_64-softmmu/hw/hyperv/vmbus.o > > >>>> /home/rtrk/Build/qemu-master/hw/hyperv/vmbus.c: In function > > >>>> ‘gpadl_iter_io’: > > >>>> /home/rtrk/Build/qemu-master/hw/hyperv/vmbus.c:386:13: error: cast > > >>>> to pointer from integer of different size [-Werror=int-to-pointer-cast] > > >>>> p = (void *)(((uintptr_t)iter->map & TARGET_PAGE_MASK) | > > >>>> off_in_page); > > >>>> ^ > > >>>> cc1: all warnings being treated as errors > > >>>> make[1]: *** [/home/rtrk/Build/qemu-master/rules.mak:69: > > >>>> hw/hyperv/vmbus.o] Error 1 > > >>>> make: *** [Makefile:527: x86_64-softmmu/all] Error 2 > > >> > > >> FWIW there is no CI job covering x86 KVM on 32-bit host build. > > >> Should this be covered? I guess the problem is no CI services > > >> provide 32-bit x86... > > > > > > You can certainly provide either a container, or install the 32-bit > > > libraries in a 64-bit environment. Then run > > > > > > PKG_CONFIG_LIBDIR=... ./configure --extra-cflags=-m32 > > > > > > and it should be possible to build 32-bit binaries, too. > > > > > > Alternatively, we could add a cross-compilation job that builds with > > > i686-w64-mingw32 in 32-bit. > > > > Oh, this case is covered: > > https://app.shippable.com/github/qemu/qemu/runs/2437/2/console > > > > But this doesn't use KVM ;) > > -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1885247 Title: Build error in Intel 32-bit hosts Status in QEMU: New Bug description: The code base is on master, checked out on Thursday June25th 2020, 0250c595c9d. The build procedure: $ mkdir build-gcc $ cd build-gcc $ ../configure $ make The build error message is: CC x86_64-softmmu/hw/hyperv/hyperv.o CC x86_64-softmmu/hw/hyperv/hyperv_testdev.o CC x86_64-softmmu/hw/hyperv/vmbus.o /home/rtrk/Build/qemu-master/hw/hyperv/vmbus.c: In function ‘gpadl_iter_io’: /home/rtrk/Build/qemu-master/hw/hyperv/vmbus.c:386:13: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast] p = (void *)(((uintptr_t)iter->map & TARGET_PAGE_MASK) | off_in_page); ^ cc1: all warnings being treated as errors make[1]: *** [/home/rtrk/Build/qemu-master/rules.mak:69: hw/hyperv/vmbus.o] Error 1 make: *** [Makefile:527: x86_64-softmmu/all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1885247/+subscriptions
next prev parent reply other threads:[~2020-06-26 11:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-26 7:04 [Bug 1885247] [NEW] Build error in Intel 32-bit hosts Aleksandar Markovic 2020-06-26 7:37 ` Aleksandar Markovic 2020-06-26 7:37 ` Aleksandar Markovic 2020-06-26 9:13 ` Philippe Mathieu-Daudé 2020-06-26 9:13 ` Philippe Mathieu-Daudé 2020-06-26 9:20 ` Thomas Huth 2020-06-26 9:27 ` Philippe Mathieu-Daudé 2020-06-26 9:27 ` Philippe Mathieu-Daudé 2020-06-26 10:54 ` Jon Doron 2020-06-26 11:20 ` Aleksandar Markovic [this message] 2020-06-26 11:20 ` Aleksandar Markovic 2020-06-26 9:10 ` [Bug 1885247] " Peter Maydell 2021-05-07 3:06 ` Thomas Huth
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='CAHiYmc7SrqDZQzEdfM7NKt=vPjmXACQF+C45R76yNEgq1VQJxw@mail.gmail.com' \ --to=aleksandar.qemu.devel@gmail.com \ --cc=1885247@bugs.launchpad.net \ --cc=alex.bennee@linaro.org \ --cc=arilou@gmail.com \ --cc=pbonzini@redhat.com \ --cc=philmd@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=thuth@redhat.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).