unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Akib Azmain Turja <akib@disroot.org>,  guix-devel@gnu.org
Subject: Re: Can't install wine, curl build fails at 'check' stage
Date: Wed, 06 Jul 2022 17:25:00 +0200	[thread overview]
Message-ID: <87iloa2rhv.fsf@gnu.org> (raw)
In-Reply-To: <86fsjgzs7s.fsf@gmail.com> (zimoun's message of "Mon, 04 Jul 2022 19:46:15 +0200")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> On Mon, 04 Jul 2022 at 15:40, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Indeed, ‘guix build
>> /gnu/store/v3kc0z1mx7zai6hky8kzlp171cxr2ccj-curl-7.84.0.drv’ fails with:
>
> [...]
>
>> Now, I don’t see where this .drv comes from.  Here’s what I see on
>> x86_64:
>
> I think it comes from a twist with i686:
>
> $ guix time-machine --commit=81cf674             \
>      -- build  --no-grafts                     \
>      -e '(@@ (gnu packages curl) curl-7.84.0)' \
>      -s i686-linux -d
> /gnu/store/v3kc0z1mx7zai6hky8kzlp171cxr2ccj-curl-7.84.0.drv

Oh I see, that’s because ‘wine’ forces #:system "i686-linux".

Efraim fixed this a couple of days ago in
c145e51844bf52eb77cdc969a0fe30a48755b29e by skipping the test.

Apparently the failure was due to a resource constraint: changing
NUM_THREADS from 1000 to 100 in lib3026.c helps makes it pass on
i686-linux.

Ludo’.


      reply	other threads:[~2022-07-06 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 16:33 Can't install wine, curl build fails at 'check' stage Akib Azmain Turja
2022-07-01 17:34 ` zimoun
2022-07-02  4:18   ` Akib Azmain Turja
2022-07-04 11:33     ` Akib Azmain Turja
2022-07-04 12:25     ` zimoun
2022-07-04 13:40 ` Ludovic Courtès
2022-07-04 17:46   ` zimoun
2022-07-06 15:25     ` Ludovic Courtès [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iloa2rhv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=akib@disroot.org \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).