all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 52081@debbugs.gnu.org
Subject: bug#52081: [core-updates-frozen] Wine fails to build; failing i686 tests
Date: Wed, 24 Nov 2021 17:28:31 +0000	[thread overview]
Message-ID: <Vf5o0WC8BlUjSN3Eca7oVCeK7jZSIRNaSx5YUYJ72YoNa7hDdyxzC3Nz7rXrglZ_yPWwyLuCednbZKbyuWzvirsp1fuP_CKnJ5yw1aNrbUw=@protonmail.com> (raw)

Hi everyone,

I was hoping the polkit/duktape patch would resolve issues with i686 builds that prevent Wine from building (on x86-64 where it needs the i686 version). While it has gotten further, it is failing due to test failures on i686 for its dependencies. I've successfully built Wine for i686 with:

guix build wine -s i686-linux --without-tests=plotutils --without-tests=glib-networking --without-tests=lib2geom --without-tests=gtk+@3.24.30

I don't know if I'll have the chance today to try to disable or fix the failing tests on i686 for these packages, which would also likely help the i686 coverage (lots of packages depend on these). If someone is more familiar with these packages and tests, that would be most helpful.

Here are the most recent failure logs on Cuirass for the packages:

plotutils (2 tests): https://ci.guix.gnu.org/build/1685012/log/raw

glib-networking (1 test): https://ci.guix.gnu.org/build/1759508/log/raw

lib2geom (1 test): https://ci.guix.gnu.org/build/1690360/log/raw

gtk+@3.24.30 (2 tests): https://ci.guix.gnu.org/build/1331231/log/raw

Hope this is helpful! If I do make any progress on patches for these tests, I'll add it to this thread.

John




             reply	other threads:[~2021-11-24 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 17:28 John Kehayias via Bug reports for GNU Guix [this message]
2021-11-26  3:31 ` bug#52081: [core-updates-frozen] Wine fails to build; failing i686 tests Maxim Cournoyer

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='Vf5o0WC8BlUjSN3Eca7oVCeK7jZSIRNaSx5YUYJ72YoNa7hDdyxzC3Nz7rXrglZ_yPWwyLuCednbZKbyuWzvirsp1fuP_CKnJ5yw1aNrbUw=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=52081@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.