From: yasu <yasu@yasuaki.com>
To: John Soo <jsoo1@asu.edu>
Cc: Bug Guix <bug-guix@gnu.org>, Help Guix <help-guix@gnu.org>
Subject: Re: Bug? Haskell GHC wont' work since ghc@8.6?
Date: Mon, 11 Jan 2021 15:04:21 +0900 [thread overview]
Message-ID: <a2d671077b83a6f7181597b36ceaf347d32b94ac.camel@yasuaki.com> (raw)
In-Reply-To: <a888661c-a888-4af0-9839-3c39176a6499@Johns-iPhone>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
Hi John,
Thank you, after installing gcc-toolchain, it worked!
Then this is indeed a bug that should be very simple to fix? Just
require gcc-toolchain (or some of its required features) as a GHC's
dependency?
I am also curious, what kind of testing (if any?) does Guix perform for
packages?? Or is GHC already marked as broken?
(Apology for repeated question marks :-))
~/co/haskell-tiny-intro/exercise (master *)$ guix install gcc-
toolchain...~/co/haskell-tiny-intro/exercise (master *)$ ghc a.hs[1 of
1] Compiling Main ( a.hs, a.o )Linking a ...~/co/haskell-
tiny-intro/exercise (master *)$ ghc --versionThe Glorious Glasgow
Haskell Compilation System, version 8.8.3
Cheers,
Yasu
On Sun, 2021-01-10 at 21:49 -0800, John Soo wrote:
> Hi yasu,
> Compiling with ghc requires a c toolchain (like gcc-toolchain)
> installed to work. Can you try again after installing gcc-toolchain?
> Ghc has not been perfect for me recently but I use it quite a lot.
>
> Hope that helps,
>
> John
[-- Attachment #2: face-smile.png --]
[-- Type: image/png, Size: 871 bytes --]
next prev parent reply other threads:[~2021-01-11 6:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 5:47 Bug? Haskell GHC wont' work since ghc@8.6? yasu
2021-01-11 5:49 ` John Soo
2021-01-11 6:04 ` yasu [this message]
2021-03-26 9:14 ` bug#45776: " zimoun
2021-03-26 11:32 ` John Soo
2021-03-26 11:55 ` Maxime Devos
-- strict thread matches above, loose matches on Subject: below --
2021-01-11 6:18 John Soo
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
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=a2d671077b83a6f7181597b36ceaf347d32b94ac.camel@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=bug-guix@gnu.org \
--cc=help-guix@gnu.org \
--cc=jsoo1@asu.edu \
/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).