From: Csepp <raingloom@riseup.net>
To: Jonas <jonas@moesys.no>
Cc: 65460@debbugs.gnu.org, paren@disroot.org
Subject: bug#65460: ghc/ghci are broken
Date: Wed, 23 Aug 2023 16:42:43 +0200 [thread overview]
Message-ID: <87il95ddk4.fsf@riseup.net> (raw)
In-Reply-To: <9740da44-a75f-440b-8bea-7e1ad3beb926@moesys.no>
Jonas via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> Thanks! Adding gcc-toolchain to the profile fixed it, but shouldn't this
> be automatically brought in by `guix install ghc`? This does still feels
> like a bug to me, shouldn't gcc-toolchain be a part of ghcs native-inputs?
>
> sanoj@deimos ~/builds/hs-hello$ guix shell --container ghc -- ghc hello.hs
> Linking hello ...
>
> <no location info>: error:
> Warning: Couldn't figure out C compiler information!
> Make sure you're using GNU gcc, or clang
> ghc: could not execute: gcc
>
> Den 8/23/23 07:14, skrev (:
>> Jonas via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
>>> And compiling a hello-world program with ghc gives me:
>>>
>>> [1 of 1] Compiling Main ( hello.hs, hello.o )
>>>
>>> <no location info>: error:
>>> Warning: Couldn't figure out C compiler information!
>>> Make sure you're using GNU gcc, or clang
>> At the risk of stating an obvious thing that you've probably already
>> tried; is `gcc-toolchain` available in the environment?
>>
>> -- (
I assume GHC can work with other toolchains, like Clang, so it's better
to be explicit about what you want to use.
next prev parent reply other threads:[~2023-08-23 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 22:57 bug#65460: ghc/ghci are broken Jonas via Bug reports for GNU Guix
2023-08-23 5:14 ` paren--- via Bug reports for GNU Guix
2023-08-23 10:39 ` Jonas via Bug reports for GNU Guix
2023-08-23 14:42 ` Csepp [this message]
2023-08-23 16:16 ` Saku Laesvuori via Bug reports for GNU Guix
2023-08-29 21:07 ` Maxim Cournoyer
2023-09-05 17:42 ` Simon Tournier
2023-08-24 7:01 ` paren--- via Bug reports for GNU Guix
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=87il95ddk4.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=65460@debbugs.gnu.org \
--cc=jonas@moesys.no \
--cc=paren@disroot.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.
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).