From: jchook <jchook@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Can't customize XMonad
Date: Fri, 15 Jan 2021 01:51:07 +0100 [thread overview]
Message-ID: <20210115005107.YYjRcvMaNmOf0Z6eSHjJst-lhgH1o9MltVOHWmyx5nA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-6414@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
New comment by jchook on void-packages repository
https://github.com/void-linux/void-packages/issues/6414#issuecomment-760547883
Comment:
According to the [cabal docs](https://cabal.readthedocs.io/en/3.4/developing-packages.html#kinds-of-package-cabal-vs-ghc-vs-system)
> Library packages have to be registered with GHC for them to be available in GHCi or to be used when compiling other programs or packages.
> When you build and install a Cabal package containing a library then it gets registered with GHC automatically.
This automatic registration **does not appear to happen** on Void, whether installed via XBPS or a `ghcup`. Cabal silently fails(?) to add libraries to the package database, even when I explicitly specify a package db.
`ghc-pkg recache` did not help.
I did get some hopeful output by passing the cabal package.db to ghc-pkg, e.g.
```sh
ghc-pkg --package-db=$HOME/.cabal/store/ghc-8.8.4/package.db
```
I'm not sure where the disconnect is between cabal and ghc-pkg.
Following https://github.com/haskell/cabal/issues/6262#issuecomment-733919670, I successfully installed xmonad using `cabal v1-install xmonad`, and it properly registered in a new package known to `ghc-pkg list`. However the package installs "hidden" by default. `ghc-pkg expose xmonad` exposed it, but running `xmonad --recompile` still fails with all the same errors. *sigh*.
So far this seems like a cabal bug. It appears to silently fail to register with GHC.
- Void glibc Linux 5.9.16 x86_64
- GHC v8.8.4
- Cabal v3.2.0.0
next prev parent reply other threads:[~2021-01-15 0:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-6414@inbox.vuxu.org>
2019-10-13 3:31 ` voidlinux-github
2020-10-15 4:22 ` Rex-Official
2020-11-18 1:13 ` chilledfrogs
2021-01-14 23:42 ` jchook
2021-01-14 23:51 ` jchook
2021-01-15 0:51 ` jchook [this message]
2021-01-15 0:51 ` jchook
2021-01-15 1:04 ` jchook
2021-01-15 1:13 ` jchook
2021-01-15 1:51 ` jchook
2021-01-15 1:52 ` jchook
2021-02-15 14:39 ` ericonr
2021-03-06 22:50 ` jchook
2021-03-13 16:04 ` xaltsc
2021-10-25 7:36 ` motorto
2021-10-25 13:22 ` ericonr
2021-10-25 15:00 ` motorto
2021-10-25 19:08 ` ericonr
2021-10-25 20:24 ` motorto
2021-10-25 22:47 ` jchook
2021-10-26 4:07 ` xaltsc
2021-10-26 4:08 ` xaltsc
2021-10-26 4:10 ` xaltsc
2021-10-26 14:48 ` woffs
2021-11-08 19:10 ` Chocimier
2021-11-08 19:10 ` [ISSUE] [CLOSED] " Chocimier
2022-02-17 14:12 ` riseekrthakur
2022-02-17 22:13 ` jchook
2022-02-18 13:47 ` riseekrthakur
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=20210115005107.YYjRcvMaNmOf0Z6eSHjJst-lhgH1o9MltVOHWmyx5nA@z \
--to=jchook@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).