I'm trying Conrad Barski's haskell tutorial[1] but it looks like
runhaskell cannot find a few packages that will be necessary in the
tutorial.
[1]:http://lisperati.com/haskell/
I installed ghc, ghc-random and ghc-regex-compat. I typed up the
program as instructed. Then I ran "runhaskell tutorial.hs
Hi Jesse,
> Can somebody help me out please?
I can try!
Can get the contents of $GHC_PACKAGE_PATH please? Guix uses this environment
variable that is recognized by the ghc toolchain to tell ghc where packages are
installed.
What happens if you try to load your file in ghci instead of using ru
On Mon, 2019-09-16 at 17:00 -0700, John Soo wrote:
> Hi Jesse,
>
> > Can somebody help me out please?
>
> I can try!
>
> Can get the contents of $GHC_PACKAGE_PATH please? Guix uses this
> environment variable that is recognized by the ghc toolchain to tell
> ghc where packages are installed.
>
Hi Jesse,
> GHC_PACKAGE_PATH did
> not change, even when I uninstalled > everything, so I suspected it was
> linked to a login script.
Ok yes. That is the state of affairs right now. The environment variables are
sourced in the login profile. You can find the variables using guix package
--se
On Mon, 2019-09-16 at 22:27 -0700, John Soo wrote:
> Hi Jesse,
>
> > GHC_PACKAGE_PATH did
> > not change, even when I uninstalled > everything, so I suspected it
> > was
> > linked to a login script.
>
> Ok yes. That is the state of affairs right now. The environment
> variables are sourced in
Hi Jesse,
> Why did ghc-random and ghc-regex-compat only work with ghc 8.4.3?
RIght now, most - if not all - ghc packages are built with ghc@8.4.3. GHC
will check the version it was compiled with and refuse to compile if there
is a mismatch between the object file and your project.
Now that I say
Hi,
John Soo writes:
> One other problem I can think of is that the current ghc is 8.6 but most
> ghc-* packages are built with 8.4 so most packages are incompatible with
> the default.
I’ve seen a number of bug reports and questions about this. Maybe we
should rename GHC 8.6 to “ghc-next” unt
Hi Tim,
> Maybe we should rename GHC 8.6 to “ghc-next” until the build system uses it.
Makes sense to me. I tried updating quickcheck for 8.6 and I think we have our
work cutout for ourselves... hopefully we can get there soon though!
- John
