emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#37361: closed (GHCI fails to run for ghc@8.6.5)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#37361: closed (GHCI fails to run for ghc@8.6.5)
Date: Tue, 10 Sep 2019 04:59:02 +0000

Your message dated Tue, 10 Sep 2019 00:58:47 -0400
with message-id <address@hidden>
and subject line Re: bug#37361: GHCI fails to run for ghc@8.6.5
has caused the debbugs.gnu.org bug report #37361,
regarding GHCI fails to run for ghc@8.6.5
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
37361: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=37361
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: GHCI fails to run for ghc@8.6.5 Date: Mon, 9 Sep 2019 15:37:24 -0500
To reproduce, just guix environment --ad-hoc ghc -- ghci. ghc@8.4.3
works. Seems like this may be related to some Prelude changes upstream
(https://gitlab.haskell.org/ghc/ghc/issues/16563), but I'm not
familiar enough with GHC internals to really tell what's going on.
Interestingly, when I try to run plain old GHC on some source files
with 8.6.5 I get another seemingly unrelated error:

    Bad interface file:
/gnu/store/8v1sn5ns7r5n02aip0b0ypyyzb2y1i1a-ghc-8.4.3/lib/ghc-8.4.3/base-4.11.1.0/Prelude.hi
            mismatched interface file versions (wanted "8065", got "8043")
      |
    1 | import Test.Hspec        (Spec, it, shouldBe)
      | ^

Again, I'm afraid I'm not entirely familiar with GHC internals and the
function of interfaces files. Nevertheless, it seems not all is well
in Guix-Haskell-land.



--- End Message ---
--- Begin Message --- Subject: Re: bug#37361: GHCI fails to run for ghc@8.6.5 Date: Tue, 10 Sep 2019 00:58:47 -0400 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)
Hi Jacob,

Jacob MacDonald <address@hidden> writes:

>> I believe this should be fixed by 83aa656217.
>
> That does indeed fix both bugs. In my specific case I'm still running
> into an issue with dependency shadowing, but it seems like a separate
> issue and I'll open a new one if it's not on my side.
>
> Thanks.

Thanks for checking so quickly.  :)


-- Tim


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]