unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Justin Garcia <purefunctor@gmail.com>
To: help-guix@gnu.org
Subject: Packaging GHC 9.2.4 -- with no prior experience
Date: Mon, 17 Oct 2022 21:32:40 +0800	[thread overview]
Message-ID: <CAOcucyTgP0D4LZ9HiDF8MRPtw3-JTDiY948p++hjevH5qSci2g@mail.gmail.com> (raw)

Hi all!

I've recently come to like Guix's approach coming from Nix, and would
definitely love to be able to use it within my development spaces.

I'd love to be able to package the latest versions of PureScript compiler (
https://github.com/purescript/purescript) for Guix, although one blocker is
that the latest GHC available is 9.0, whereas we currently build PureScript
against GHC 9.2.3 exclusively; eventually, that'll get bumped up to 9.2.4,
and then 9.4.2 but that will be in the following months.

With no prior experience, I decided to try and write a package declaration
for GHC 9.2.4, which can be found here:
https://github.com/akashi-moe/akashi/blob/main/akashi/packages/haskell.scm

Note that unlike GHC 9.0, this uses the Hadrian build system packaged
alongside GHC instead of Make, which is slowly being phased out by the GHC
development team.

I got pretty far this weekend, although the package declaration fails
currently during the `validate-runpath` phase, which I assume is because of
the `install` command that I used. Given that I'm on a pretty slow machine
currently, it's rather difficult to iterate when I have to wait 1h~1h30m
between builds.

I'd greatly appreciate it if anyone wants to take a look.

Kind regards,
purefunctor

             reply	other threads:[~2022-10-17 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 13:32 Justin Garcia [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-19  0:50 Packaging GHC 9.2.4 -- with no prior experience Justin Garcia via

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=CAOcucyTgP0D4LZ9HiDF8MRPtw3-JTDiY948p++hjevH5qSci2g@mail.gmail.com \
    --to=purefunctor@gmail.com \
    --cc=help-guix@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.
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).