qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Aleksandar Markovic" <aleksandar.qemu.devel@gmail.com>,
	"Bug 1885247" <1885247@bugs.launchpad.net>,
	arilou@gmail.com, "Paolo Bonzini" <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Bug 1885247] [NEW] Build error in Intel 32-bit hosts
Date: Fri, 26 Jun 2020 11:20:30 +0200	[thread overview]
Message-ID: <d2657f75-26fe-117b-183d-732d88da2653@redhat.com> (raw)
In-Reply-To: <b34bf27c-3189-addc-0c50-b0c0c533876d@redhat.com>

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.

  Thomas



  parent reply	other threads:[~2020-06-26  9: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 [this message]
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
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=d2657f75-26fe-117b-183d-732d88da2653@redhat.com \
    --to=thuth@redhat.com \
    --cc=1885247@bugs.launchpad.net \
    --cc=aleksandar.qemu.devel@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=arilou@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 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).