qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Di Federico via <qemu-devel@nongnu.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: tsimpson@quicinc.com, Anton Johansson via <qemu-devel@nongnu.org>,
	Brian Cain <bcain@quicinc.com>
Subject: QEMU CI failure of cross-i386-* targets (meson picks wrong glib for native target)
Date: Fri, 24 Dec 2021 11:34:02 +0100	[thread overview]
Message-ID: <20211224113402.6d2d54f9@orange> (raw)

Hi Paolo, I'm trying to get the QEMU CI run successfully for the
idef-parser patchset. However I'm facing an issue I haven't been able
to work around with meson. Maybe you can help?

The failing tests are cross-i386-*

    https://gitlab.com/carl.cudig/qemu/-/jobs/1437392669
    https://gitlab.com/carl.cudig/qemu/-/jobs/1437392673
    https://gitlab.com/carl.cudig/qemu/-/jobs/1437392671

I think the problem is that we're adding a new build-time dependency:
glib. However glib is also a run-time dependency and, AFAIU, when cross
compiling for x86 on a x86-64 machine, if you create a native
executable, meson picks up the x86 version of glib (as opposed to the
x86-64).

I've been fiddling with this for a while, unsuccessfully.

Relevant portion of the code:

    https://gitlab.com/carl.cudig/qemu/-/commit/c020958c37fa723f7e933a58b1bb1c3668ff4cff#8145a41027f26ff426d5a2c8b00c56f227943165_198_202

Happy holidays!

-- 
Alessandro Di Federico
rev.ng Labs Srl


             reply	other threads:[~2021-12-24 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24 10:34 Alessandro Di Federico via [this message]
2021-12-24 21:25 ` QEMU CI failure of cross-i386-* targets (meson picks wrong glib for native target) Paolo Bonzini
2021-12-29 11:03   ` Alessandro Di Federico via

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=20211224113402.6d2d54f9@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 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).