all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 64643-done@debbugs.gnu.org
Subject: bug#64643: [PATCH] gnu: ghc-8.10: Fix build on i686-linux.
Date: Mon, 17 Jul 2023 13:58:56 +0100	[thread overview]
Message-ID: <87r0p6y9pc.fsf@cbaines.net> (raw)
In-Reply-To: <ZLOydxjDGpotMhL2@noor.fritz.box>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]


Lars-Dominik Braun <lars@6xq.net> writes:

> Hi,
>
>> Yep, you can click the "View build on https://bordeaux.guix.gnu.org"
>> links from this page [1] to find the build logs for all the failing
>> builds.
>>
>> 1: https://data.qa.guix.gnu.org/gnu/store/sp4csvzxjzzjhmyp7sfdxg3ypqpysh2a-ghc-8.10.7.drv
>
> huh, a segfault. Weird. Perhaps it’s running out of address space.
>
>> And yes, this patch only affects i686-linux as confirmed by [2].
>
> Ah, you’re right. I missed this patch context:
>
>>           #$@(if (string-prefix? "i686" (or (%current-target-system)
>>                                             (%current-system)))
>
> Looks good to me then!

Great, I've pushed this to master as
ad08f9331fee7a8e71e94b02f86f54ab3e1001a8.

There's ~2000 affected packages, but I think this is OK since at least
for the bordeaux build farm, these packages are being unblocked rather
than rebuilt, and for ci, it'll take no time at all to catch up.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

      reply	other threads:[~2023-07-17 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15  9:39 [bug#64643] [PATCH] gnu: ghc-8.10: Fix build on i686-linux Christopher Baines
2023-07-16  8:29 ` Lars-Dominik Braun
2023-07-16  8:41   ` Christopher Baines
2023-07-16  9:03     ` Lars-Dominik Braun
2023-07-17 12:58       ` Christopher Baines [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=87r0p6y9pc.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=64643-done@debbugs.gnu.org \
    --cc=lars@6xq.net \
    /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.