From: Uwe Brauer <oub-YB6e1s5WF/He5aOfsHch1g@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Mac 10.15 compiling using ghc
Date: Sat, 01 May 2021 13:11:03 +0200 [thread overview]
Message-ID: <m2h7jm675k.fsf@mat.ucm.es> (raw)
In-Reply-To: <m2v983387x.fsf@MacBook-Pro.hsd1.ca.comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
>>> "JM" == John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:
> Although with the old version of cabal you have, it might
> work just to do
> cabal install pandoc-types
> and then ghc --make as before.
Not sure my answer went through.
I followed your advice and obtained
,----
|
| I tried that but obtained
| Text/Pandoc/Legacy/Definition.hs:103:14: parse error on input ‘{’
| cabal: Error: some packages failed to install:
| pandoc-types-1.20 failed during the building phase. The exception was:
| ExitFailure 1
`----
Then I tried cabal install cabal-install
And obtained
,----
| cabal: Error: some packages failed to install:
| Cabal-3.0.2.0 failed during the configure step. The exception was:
| user error ('/opt/sw/bin/ghc' exited with an error:
|
| /var/folders/j1/7bbsk0jj6nxd5yxndqwvb1t00000gn/T/cabal-tmp-29800/Cabal-3.0.2.0/Distribution/Parsec.hs:134:7:
| error: function-like macro 'MIN_VERSION_base' is not defined
| #if !(MIN_VERSION_base(4,13,0))
| ^
| 1 error generated.
| )
| cabal-install-3.0.0.0 depends on Cabal-3.0.2.0 which failed to install.
| hackage-security-0.5.3.0 depends on Cabal-3.0.2.0 which failed to install.
|
`----
Sigh, I don't recall a time where this worked flawlessly.
Andy advice would be welcome, I shall also ask on the fink mailing list.
An alternative would be to un install fink's cabal pkg and try to
install it directly.
Regards
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m2h7jm675k.fsf%40mat.ucm.es.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2021-05-01 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 13:18 Uwe Brauer
[not found] ` <87wnsjewqw.fsf-YB6e1s5WF/He5aOfsHch1g@public.gmane.org>
2021-04-30 15:31 ` John MacFarlane
[not found] ` <m2im436b7h.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-04-30 15:34 ` John MacFarlane
2021-04-30 16:25 ` Uwe Brauer
[not found] ` <87czubeo4d.fsf-YB6e1s5WF/He5aOfsHch1g@public.gmane.org>
2021-04-30 19:03 ` John MacFarlane
[not found] ` <m2y2cz389c.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-04-30 19:04 ` John MacFarlane
2021-05-01 11:11 ` Uwe Brauer [this message]
2021-05-02 17:53 ` [some success] (was: Mac 10.15 compiling using ghc) Uwe Brauer
[not found] ` <m27dkhc9a5.fsf_-_-YB6e1s5WF/He5aOfsHch1g@public.gmane.org>
2021-05-02 20:33 ` John MacFarlane
2021-05-03 7:18 ` [some success] Uwe Brauer
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=m2h7jm675k.fsf@mat.ucm.es \
--to=oub-yb6e1s5wf/he5aofshch1g@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).