From: John Soo <jsoo1@asu.edu>
To: yasu <yasu@yasuaki.com>
Cc: Bug Guix <bug-guix@gnu.org>, Help Guix <help-guix@gnu.org>
Subject: Bug? Haskell GHC wont' work since ghc@8.6?
Date: Sun, 10 Jan 2021 22:18:24 -0800 [thread overview]
Message-ID: <dc920069-2cda-47e8-8c74-8bf74f6292c6@Johns-iPhone> (raw)
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Hi yasu,
This question comes up on the mailing list every so often, but I don’t think it is a bug. I want to be able to choose the c toolchain ghc uses myself. I would rather introduce some Haskell specific documentation.
We discussed during the guix day that we would love to have some language specific setup documentation. I had issues like this in mind.
- John
[-- Attachment #2: face-smile.png --]
[-- Type: image/PNG, Size: 871 bytes --]
next reply other threads:[~2021-01-11 6:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 6:18 John Soo [this message]
2021-01-11 6:31 ` bug#45778: Bug? Haskell GHC wont' work since ghc@8.6? yasu
2021-01-11 14:54 ` zimoun
2021-01-11 15:14 ` John Soo
2021-01-11 18:42 ` Vincent Legoll
2021-01-11 20:47 ` John Soo
-- strict thread matches above, loose matches on Subject: below --
2021-01-11 5:47 yasu
2021-01-11 5:49 ` John Soo
2021-01-11 6:04 ` yasu
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=dc920069-2cda-47e8-8c74-8bf74f6292c6@Johns-iPhone \
--to=jsoo1@asu.edu \
--cc=bug-guix@gnu.org \
--cc=help-guix@gnu.org \
--cc=yasu@yasuaki.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 read-only IMAP folder(s) and NNTP newsgroup(s).