From: "Philip Munksgaard" <philip@munksgaard.me>
To: 53655@debbugs.gnu.org
Subject: bug#53655: haskell build system cannot build attoparsec
Date: Wed, 23 Feb 2022 12:25:36 +0100 [thread overview]
Message-ID: <a4f7dd5f-e162-426b-9e42-dc0c31b4507c@www.fastmail.com> (raw)
In-Reply-To: <62174ccd-9114-4096-8d63-e1933b76ad32@www.fastmail.com>
On Wed, 23 Feb 2022, at 12:06, Philip Munksgaard wrote:
> And yes, this is indeed the issue I'm mostly concerned about. It seems
> like
> `/gnu/store/25ql0xsjqf0alrvy6hmpw6gzirzbqfmv-ghc-attoparsec-0.14.4/ghc-attoparsec-0.14.4.conf`
> is expected to be a file, while it is in fact a directory. I'm not sure
> what that means or why it is important though.
Upon further investigation, it seems like the `register` function in `guix/build/haskell-build-system.scm` assumes that running `runhaskell Setup.hs register --gen-pkg-config=...` will at most result in a single configuration file, while the documentation for `--gen-pkg-config` clearly states that it is also possible that it results in a directory[0].
The relevant section states:
> This option outputs a directory if the package requires multiple registrations: this can occur if internal/convenience libraries are used. These configuration file names are sorted so that they can be registered in order.
I think we need to amend `haskell-build-system.scm` to be able to handle such cases.
0: https://downloads.haskell.org/cabal/Cabal-3.0.0.0/doc/users-guide/installing-packages.html#cmdoption-setup-register-gen-pkg-config
next prev parent reply other threads:[~2022-02-23 11:39 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
2022-02-23 11:06 ` Philip Munksgaard
2022-02-23 11:25 ` Philip Munksgaard [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4f7dd5f-e162-426b-9e42-dc0c31b4507c@www.fastmail.com \
--to=philip@munksgaard.me \
--cc=53655@debbugs.gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).