From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] GHC/Stack build failures on i686
Date: Tue, 27 Jul 2021 22:27:37 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32221@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
New issue by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/32221
Description:
First noticed building darcs:
https://build.voidlinux.org/builders/i686_builder/builds/33610/steps/shell_3/logs/stdio
Marking that broken to clear the log jam, it also tripped up on debug-me:
https://build.voidlinux.org/builders/i686_builder/builds/33611/steps/shell_3/logs/stdio
This seems like a widespread problem.
cc: @slotThe
next reply other threads:[~2021-07-27 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 20:27 ahesford [this message]
2021-07-28 5:04 ` ericonr
2021-07-28 6:31 ` ericonr
2021-07-28 7:20 ` slotThe
2021-07-28 12:51 ` [ISSUE] [CLOSED] " leahneukirchen
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32221@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).