From: Alessandro Di Federico via <qemu-devel@nongnu.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Brian Cain <bcain@quicinc.com>,
Taylor Simpson <tsimpson@quicinc.com>,
Anton Johansson <qemu-devel@nongnu.org>
Subject: Re: QEMU CI failure of cross-i386-* targets (meson picks wrong glib for native target)
Date: Wed, 29 Dec 2021 12:03:25 +0100 [thread overview]
Message-ID: <20211229120325.1e593deb@orange> (raw)
In-Reply-To: <CABgObfZWaeo2yQLvgHNhA443yqZLtcSusbms8hUafx-KuYXUaA@mail.gmail.com>
On Fri, 24 Dec 2021 22:25:24 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
> Is the configure script setting $cross_compile to yes? That will
> decide whether meson getting a --cross-file or a --native-file
> option, and consequently whether it treats the host and build
> machines as equal or different.
From what I can see cross_compile is set only if --cross-prefix is set,
which doesn't seem to be the case for most containers (e.g., s390x)
but not for i386:
tests/docker/dockerfiles/debian-s390x-cross.docker:ENV QEMU_CONFIGURE_OPTS --cross-prefix=s390x-linux-gnu-
tests/docker/dockerfiles/fedora-i386-cross.docker:ENV QEMU_CONFIGURE_OPTS --cpu=i386 --disable-vhost-user
I can try to set `--cross-prefix=x86_64-redhat-linux-` but I guess this
will prevent certain tests to run (given the cross-compile environment).
I'll give it a shot.
--
Alessandro Di Federico
rev.ng Labs Srl
prev parent reply other threads:[~2021-12-29 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 10:34 QEMU CI failure of cross-i386-* targets (meson picks wrong glib for native target) Alessandro Di Federico via
2021-12-24 21:25 ` Paolo Bonzini
2021-12-29 11:03 ` Alessandro Di Federico via [this message]
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=20211229120325.1e593deb@orange \
--to=qemu-devel@nongnu.org \
--cc=ale@rev.ng \
--cc=bcain@quicinc.com \
--cc=pbonzini@redhat.com \
--cc=tsimpson@quicinc.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: 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.