From: zimoun <zimon.toutoune@gmail.com>
To: Philip Munksgaard <philip@munksgaard.me>, 53655@debbugs.gnu.org
Subject: bug#53655: haskell build system cannot build attoparsec
Date: Wed, 23 Feb 2022 11:02:31 +0100 [thread overview]
Message-ID: <86a6eh2954.fsf@gmail.com> (raw)
In-Reply-To: <a9871314-33e8-474e-b2ec-854a5c740bfb@www.fastmail.com>
Hi,
Thanks for he report.
It is 2 different issues; therefore I propose to keep them separated.
On Mon, 31 Jan 2022 at 11:33, "Philip Munksgaard" <philip@munksgaard.me> wrote:
> ```
> $ guix import hackage -r attoparsec
[...]
>
> guix/import/utils.scm:492:33: In procedure lookup-node:
> Wrong number of values returned to continuation (expected 2)
> ```
This one is about the importer. I think it comes from the current
cabal.scm parser; not able to deal with:
--8<---------------cut here---------------start------------->8---
-- We need to test and benchmark these modules,
-- but do not want to expose them to end users
library attoparsec-internal
hs-source-dirs: internal
build-depends: array,
[...]
library
build-depends: array,
[...]
attoparsec-internal
--8<---------------cut here---------------end--------------->8---
Could you open another bug report for that?
Let focus on this one…
> When trying to build this file however, I get the following error:
>
> ```
> running "runhaskell Setup.hs" with command "register" and parameters ("--gen-pkg-config=/gnu/store/25ql0xsjqf0alrvy6hmpw6gzirzbqfmv-ghc-attoparsec-0.14.4/ghc-attoparsec-0.14.4.conf")
> error: in phase 'register': uncaught exception:
> ```
…for this bug report. Hum, I do not know how where the error comes
from.
Cheers,
simon
next prev parent reply other threads:[~2022-02-23 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 10:33 bug#53655: haskell build system cannot build attoparsec Philip Munksgaard
2022-02-23 10:02 ` zimoun [this message]
2022-02-23 11:06 ` Philip Munksgaard
2022-02-23 11:25 ` Philip Munksgaard
2022-02-23 13:57 ` zimoun
2022-04-06 19:27 ` zimoun
2022-04-07 8:23 ` Philip Munksgaard
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=86a6eh2954.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=53655@debbugs.gnu.org \
--cc=philip@munksgaard.me \
/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.