From: Simon Tournier <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Saku Laesvuori <saku@laesvuori.fi>
Cc: 65460-done@debbugs.gnu.org, paren@disroot.org,
Csepp <raingloom@riseup.net>, Jonas <jonas@moesys.no>
Subject: bug#65460: ghc/ghci are broken
Date: Tue, 05 Sep 2023 19:42:34 +0200 [thread overview]
Message-ID: <86o7igqzxx.fsf@gmail.com> (raw)
In-Reply-To: <87bkep8sm7.fsf@gmail.com>
Hi Maxim,
On Tue, 29 Aug 2023 at 17:07, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> For building tools requiring a compiler, the current expectation across
> Guix packages is that the user provides the one it wants. Even if using
> GCC, you may want to use a different version, and rebuilding GHC just to
> do so is... expensive.
Well, I have a patch series somewhere on my disk that adds ghc-toolchain
and hides ghc, similarly as gcc-toolchain. Somehow, I think that, “guix
shell ghc-toolchain” should just work out-of-the-box. And the
replacement of the C toolchain would be done with the package
transformation with-c-toolchain.
Bah, the series needs polishing… arf!
Cheers,
simon
next prev parent reply other threads:[~2023-09-05 19:02 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
2023-08-29 21:07 ` Maxim Cournoyer
2023-09-05 17:42 ` Simon Tournier [this message]
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=86o7igqzxx.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=65460-done@debbugs.gnu.org \
--cc=jonas@moesys.no \
--cc=maxim.cournoyer@gmail.com \
--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).