From: Timothy Sample <samplet@ngyro.com>
To: John Soo <jsoo1@asu.edu>
Cc: guix-devel@gnu.org
Subject: Re: Haskell dependencies for custom cabal builds
Date: Tue, 12 Feb 2019 14:18:40 -0500 [thread overview]
Message-ID: <87imxoak8f.fsf@ngyro.com> (raw)
In-Reply-To: <6E48CD3A-9511-4855-8C0D-DC7574546939@asu.edu> (John Soo's message of "Tue, 12 Feb 2019 08:50:32 -0800")
Hi John,
John Soo <jsoo1@asu.edu> writes:
> Hi there,
>
> I did a little digging this morning and it seems like runhaskell is
> probably deprecated in favor of runghc. Do we expect anyone to be
> using hugs or jhc? Runghc also supports ghc flags. I still need to do
> some more research here but the Haskell configure phase deliberately
> unsets GHC_PACKAGE_PATH. I assume it does this because runhaskell
> supports many Haskell compilers. If custom cabal builds are rare, I
> would suspect that non-ghc builds are even rarer. Would it be possible
> to replace runhaskell with runghc? Or parameterize the command?
I don’t see how this would help.
From the build system code,
Cabal errors if GHC_PACKAGE_PATH is set during 'configure', so unset
and restore it.
The issue that git-annex has is that it wants to use some packages
before calling into Cabal. If “GHC_PACKAGE_PATH” is set properly, it
will find the packages, proceed normally until calling Cabal, and then
error because Cabal doesn’t like “GHC_PACKAGE_PATH”. Cabal wants to
setup the package search path from the command line arguments instead.
On the other hand, if “GHC_PACKAGE_PATH” is not set, Cabal would
theoretically work, but we never get there! The custom “Setup.hs” code
errors out with missing packages before ever calling Cabal.
I don’t think that switching from “runhaskell” to “runghc” changes that.
-- Tim
next prev parent reply other threads:[~2019-02-12 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 16:37 Haskell dependencies for custom cabal builds John Soo
2019-02-11 20:19 ` Timothy Sample
2019-02-11 21:56 ` John Soo
2019-02-12 16:06 ` Timothy Sample
2019-02-12 16:50 ` John Soo
2019-02-12 19:18 ` Timothy Sample [this message]
2019-02-12 19:21 ` Timothy Sample
2019-02-12 19:37 ` John Soo
2019-02-12 19:44 ` Marius Bakke
2019-02-13 0:02 ` John Soo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imxoak8f.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.