From: "Axel Kielhorn (Pandoc)" <Pandoc-Mm1VAy9jqyoZTkkHcba27w@public.gmane.org>
To: Pandoc discuss discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Build error: cabal: Cannot build the executables in the package pandoc
Date: Sun, 25 Sep 2022 11:59:32 +0200 [thread overview]
Message-ID: <0F6FF81C-8FE4-411C-BAC5-6A7D1A9A314F@axelkielhorn.de> (raw)
Hello,
I tried to update pandoc but get a build error:
pandoc % cabal build master
Resolving dependencies...
Up to date
pandoc % cabal install
Wrote tarball sdist to
.../pandoc/dist-newstyle/sdist/pandoc-2.19.2.tar.gz
Wrote tarball sdist to
.../pandoc/dist-newstyle/sdist/pandoc-server-0.1.tar.gz
Wrote tarball sdist to
.../pandoc/dist-newstyle/sdist/pandoc-cli-0.1.tar.gz
Wrote tarball sdist to
.../pandoc/dist-newstyle/sdist/commonmark-extensions-0.2.3.2.tar.gz
Wrote tarball sdist to
.../pandoc/dist-newstyle/sdist/skylighting-format-blaze-html-0.1.1.tar.gz
Wrote tarball sdist to
.../pandoc/dist-newstyle/sdist/texmath-0.12.5.2.tar.gz
Wrote tarball sdist to
.../pandoc/dist-newstyle/sdist/gridtables-0.0.3.0.tar.gz
Resolving dependencies...
cabal: Cannot build the executables in the package pandoc because it does not
contain any executables. Check the .cabal file for the package and make sure
that it properly declares the components that you expect.
pandoc % cabal --version master
cabal-install version 3.6.2.0
compiled using version 3.6.2.0 of the Cabal library
This happens on macOS 11
The version before
bd1d923b86edba6e090ba14b1cd17e1e32c727f2
builds fine.
Greetings Axel
next reply other threads:[~2022-09-25 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 9:59 Axel Kielhorn (Pandoc) [this message]
[not found] ` <0F6FF81C-8FE4-411C-BAC5-6A7D1A9A314F-Mm1VAy9jqyoZTkkHcba27w@public.gmane.org>
2022-09-25 15:06 ` Albert Krewinkel
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=0F6FF81C-8FE4-411C-BAC5-6A7D1A9A314F@axelkielhorn.de \
--to=pandoc-mm1vay9jqyoztkkhcba27w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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).