From: Ricardo Wurmus <rekado@elephly.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: guix-devel@gnu.org
Subject: bug#33922: failing git-annex build
Date: Sun, 30 Dec 2018 12:36:59 +0100 [thread overview]
Message-ID: <87bm53gs9w.fsf@elephly.net> (raw)
In-Reply-To: <87h8evvjr2.fsf@kyleam.com>
Hi Kyle,
> I'm seeing the failure below when trying to build git-annex. Can anyone
> else reproduce this failure? Any ideas how to resolve it?
>
> --8<---------------cut here---------------start------------->8---
> % git describe
> v0.16.0-400-g4f36d98f7b
>
> % ./pre-inst-env guix build -K --check git-annex
> Utility/Exception.hs:29:1: error:
> Bad interface file: /gnu/store/qb3knv1h536sdjqc4nfkm3j1l8n7q87a-ghc-exceptions-0.10.0/lib/ghc-8.4.3/exceptions-0.10.0/Control/Monad/Catch.dyn_hi
> Something is amiss; requested module exceptions-0.10.0:Control.Monad.Catch differs from name found in the interface file exceptions-0.10.0:Control.Monad.Catch (if these names look the same, try again with -dppr-debug)
> |
> 29 | import Control.Monad.Catch as X hiding (Handler)
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It seems to me that this is a more general problem affecting all of our
Haskell packages. The configure phase that you didn’t paste should show
that modules are provided by slightly different packages.
The haskell-build-system suffers from non-determinism. It might just be
limited to the package database files that are generated by ghc-pkg
(where readdir is used and the result isn’t sorted).
I’m opening a bug report for this issue.
--
Ricardo
next prev parent reply other threads:[~2018-12-30 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 2:19 failing git-annex build Kyle Meyer
2018-12-30 11:36 ` Ricardo Wurmus [this message]
2018-12-30 15:46 ` Kyle Meyer
2019-01-02 22:14 ` bug#33922: " Timothy Sample
2019-01-05 20:12 ` Kyle Meyer
2019-01-12 7:42 ` Ricardo Wurmus
2019-01-12 15:54 ` Timothy Sample
2019-01-15 18:48 ` Timothy Sample
2019-01-17 17:33 ` Ricardo Wurmus
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=87bm53gs9w.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=kyle@kyleam.com \
/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.