unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Bone Baboon <bone.baboon@disroot.org>
To: Gary Johnson <lambdatronic@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Haskell program build and run using Cabal
Date: Sun, 11 Apr 2021 13:31:03 -0400	[thread overview]
Message-ID: <87pmz0enjc.fsf@disroot.org> (raw)
In-Reply-To: <87k0p9m0d3.fsf@disroot.org>

Gary Johnson writes:
> Guix System (unsurprisingly) has a built-in preference for building
> packages with Guix. For building Haskell programs, check out the
> `haskell-build-system`, which uses cabal and ghc under the hood.
>
> Also, if the package you want to install exists on Hackage
> (https://hackage.haskell.org) but doesn't have a corresponding Guix
> package, you should check out the Guix hackage importer:
>
> $ guix import hackage -r PACKAGE-NAME@VERSION
>
> This can auto-generate a Guix package definition for the corresponding
> Hackage package that you can then use to install it through Guix.
>
> Finally, to answer your question about environment variables, you should
> stick them in your home directory under your shell configuration script
> (e.g., ~/.bashrc, ~/.bash_profile).

Thank you for your helpful reply.

These are the two lines I added to my `.bashrc` that resolve the error
I was getting:

```
unset GHC_PACKAGE_PATH
export LD_LIBRARY_PATH=/run/current-system/profile/lib/
```
Note: The LD_LIBRARY_PATH variables was empty. If it was not I would
have appended to the existing LD_LIBRARY_PATH variable.


      parent reply	other threads:[~2021-04-11 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11  3:23 Haskell program build and run using Cabal Bone Baboon
2021-04-11 13:12 ` Gary Johnson
2021-04-11 16:11   ` John Soo
2021-04-11 17:31   ` Bone Baboon [this message]

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=87pmz0enjc.fsf@disroot.org \
    --to=bone.baboon@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=lambdatronic@disroot.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).