unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: 51213@debbugs.gnu.org
Subject: bug#51213: ghci missing reference to gcc
Date: Sun, 17 Oct 2021 00:11:03 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.2110162324520.4243@marsh.hcoop.net> (raw)
In-Reply-To: <alpine.DEB.2.21.2110141553240.4243@marsh.hcoop.net>

On Thu, 14 Oct 2021, Jack Hill wrote:

> Hi Guix,
>
> Using Guix 5fafb6e792c1e18ec223f0c7fb350d0c9b962a45, running ghci in an 
> environment can't find gcc:

Some more observations about this problem. It only occurs with our two 
newest GHC packages (8.10.7 and 8.8.4), previous releases start ghci and 
perform light usage fine. However, all releases fail to build executables 
without gcc-toolchain in the path:

```
jackhill@alperton /tmp [env]$ ghc hello.hs 
[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
ghc: could not execute: gcc
jackhill@alperton /tmp [env]$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 8.10.7
```

Interestingly, clang-toolchain can be substituted for gcc-toolchain to get 
a working ghci, but with 8.10.7, compiling with gcc still doesn't work, 
but ghc 7.10.2 find clang-toolchain to be satisfactory.

Best,
Jack




  reply	other threads:[~2021-10-17  4:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 20:00 bug#51213: ghci missing reference to gcc Jack Hill
2021-10-17  4:11 ` Jack Hill [this message]
2023-09-22 16:19 ` Simon Tournier
2023-09-23  1:23   ` Jack Hill

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=alpine.DEB.2.21.2110162324520.4243@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=51213@debbugs.gnu.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).