From: Ricardo Wurmus <rekado@elephly.net>
To: Vasilii Kolobkov <vasilii@orangeshoelaces.net>
Cc: help-guix@gnu.org
Subject: Re: Issues with Haskell's ghc
Date: Mon, 01 Jul 2019 23:43:09 +0200 [thread overview]
Message-ID: <87o92dv3bm.fsf@elephly.net> (raw)
In-Reply-To: <877e91vfla.fsf@orangeshoelaces.net>
Hi Vasilii,
> I've run aground with Haskell's ghc (interpreter works fine) - running
> ghc on a basic hello world program fails. I identified couple issues:
>
> - Include directory for linux headers wasn't passed to gcc
> (`C_INCLUDE_PATH=/gnu/... ghc` fixed it)
> - Lib C's crti.o and crt1.o where not found during linking
> (fixed with `LIBRARY_PATH=/gnu/... ghc`)
These two points sound like “gcc-toolchain” should be installed
alongside GHC.
--
Ricardo
next prev parent reply other threads:[~2019-07-01 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 17:18 Issues with Haskell's ghc Vasilii Kolobkov
2019-07-01 21:43 ` Ricardo Wurmus [this message]
2019-07-02 12:50 ` Vasilii Kolobkov
-- strict thread matches above, loose matches on Subject: below --
2019-08-03 10:15 Prateem Mandal
2019-08-04 12:35 ` Ricardo Wurmus
2019-08-04 18:41 ` Prateem Mandal
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=87o92dv3bm.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=vasilii@orangeshoelaces.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.
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).