unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Saku Laesvuori via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Csepp <raingloom@riseup.net>
Cc: 65460@debbugs.gnu.org, paren@disroot.org, Jonas <jonas@moesys.no>
Subject: bug#65460: ghc/ghci are broken
Date: Wed, 23 Aug 2023 19:16:14 +0300	[thread overview]
Message-ID: <20230823161614.zhc3cnjjipkqjfy7@X-kone> (raw)
In-Reply-To: <87il95ddk4.fsf@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

> > 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?

native-inputs are for buildtime inputs and here ghc needs a c toolchain
at runtime to compile another haskell program so gcc-toolchain should be
in "normal" inputs.

> I assume GHC can work with other toolchains, like Clang, so it's better
> to be explicit about what you want to use.

I think it would still be good to have a c toolchain as an input. Guix
packages are, if I understand correctly, supposed to work without having
to explicitly install their dependencies. If someone wants to use a
different c toolchain than the default, they can use a package
transformation to change it.

Maybe we could even have the current ghc as a hidden package and have
the public package wrap the hidden ghc adding gcc-toolchain to it's
environment, so that changing the c toolchain wouldn't require
rebuilding ghc.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-08-23 16:18 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
2023-08-23 16:16       ` Saku Laesvuori via Bug reports for GNU Guix [this message]
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=20230823161614.zhc3cnjjipkqjfy7@X-kone \
    --to=bug-guix@gnu.org \
    --cc=65460@debbugs.gnu.org \
    --cc=jonas@moesys.no \
    --cc=paren@disroot.org \
    --cc=raingloom@riseup.net \
    --cc=saku@laesvuori.fi \
    /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).