From: Leonard Rosenthol <leonardr-bM6h3K5UM15l57MIdRCFDg@public.gmane.org>
To: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Problems building current master
Date: Thu, 10 Sep 2020 20:03:38 -0400 [thread overview]
Message-ID: <CALu=v3K==wDjAhx1G3YGQMXDgVYe7tOWSvMvz40gYMMXGtRE1w@mail.gmail.com> (raw)
In-Reply-To: <m2imclqji1.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 5636 bytes --]
Assuming I understood what you meant by build with the embed_data_files
flag off, I tried.
xxxxx:pandoc-LR xxxxx$ stack build --flag pandoc:-embed_data_files
Building all executables for `pandoc' once. After a successful build of all
of them, only specified executables will be rebuilt.
pandoc> configure (lib + exe)
Configuring pandoc-2.10.1...
pandoc> build (lib + exe)
Preprocessing library for pandoc-2.10.1..
Building library for pandoc-2.10.1..
[ 1 of 171] Compiling Text.Pandoc.App.FormatHeuristics
[ 2 of 171] Compiling Text.Pandoc.Asciify
[ 3 of 171] Compiling Text.Pandoc.CSV
[ 4 of 171] Compiling Paths_pandoc
[ 5 of 171] Compiling Text.Pandoc.Emoji
[ 6 of 171] Compiling Text.Pandoc.Extensions
<command line>: can't load .so/.DLL for:
/Users/lrosenth/.stack/snapshots/x86_64-osx/a4b9df8230b44b4d1656bd3420d752e1440163e4e9d142f613e0f472365ab993/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHScommonmark-pandoc-0.2.0.0-D01mbkJUemk7h72RuTUjAh-ghc8.6.5.dylib
(dlopen(/Users/lrosenth/.stack/snapshots/x86_64-osx/a4b9df8230b44b4d1656bd3420d752e1440163e4e9d142f613e0f472365ab993/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHScommonmark-pandoc-0.2.0.0-D01mbkJUemk7h72RuTUjAh-ghc8.6.5.dylib,
5): Symbol not found:
_pandoczmtypeszm1zi21zmLb7evYKD6jv46JnhbWrkOK_TextziPandocziBuilder_normalizzeTableFootzunormalizzeRowszq_closure
Referenced from:
/Users/lrosenth/.stack/snapshots/x86_64-osx/a4b9df8230b44b4d1656bd3420d752e1440163e4e9d142f613e0f472365ab993/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHScommonmark-pandoc-0.2.0.0-D01mbkJUemk7h72RuTUjAh-ghc8.6.5.dylib
Expected in:
/Users/lrosenth/.stack/snapshots/x86_64-osx/0bf2dc0c6fb03a8a3c3fd1819c92943191347f522011fdc733a961a0bb6b76dc/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHSpandoc-types-1.21-Lb7evYKD6jv46JnhbWrkOK-ghc8.6.5.dylib
in
/Users/lrosenth/.stack/snapshots/x86_64-osx/a4b9df8230b44b4d1656bd3420d752e1440163e4e9d142f613e0f472365ab993/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHScommonmark-pandoc-0.2.0.0-D01mbkJUemk7h72RuTUjAh-ghc8.6.5.dylib)
-- While building package pandoc-2.10.1 using:
/Users/lrosenth/.stack/setup-exe-cache/x86_64-osx/Cabal-simple_mPHDZzAJ_2.4.0.1_ghc-8.6.5
--builddir=.stack-work/dist/x86_64-osx/Cabal-2.4.0.1 build lib:pandoc
exe:pandoc --ghc-options " -fdiagnostics-color=always"
Process exited with code: ExitFailure 1
On Thu, Sep 10, 2020 at 7:50 PM John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
>
> I've seen this before. It tends to happen when we use stack to
> include a repository version of a dependency like
> pandoc-citeproc.
>
> You might try removing your .stack-work directory.
>
> You might also try building with the embed_data_files flag off, then
> building again with it on.
>
> Or use cabal instead of stack?
>
> Leonard Rosenthol <leonardr-bM6h3K5UM15l57MIdRCFDg@public.gmane.org> writes:
>
> > I just pulled the latest code from master, so that I could start on my
> next
> > PR - but when trying to build, it fails right off at Text.Pandoc.Data.
> >
> > This is after a `stack clean` (just to make sure!)...
> >
> > What am I missing?
> >
> > Thanks,
> > Leonard
> > ______________
> >
> > [ 4 of 172] Compiling Text.Pandoc.Data
> > <command line>: can't load .so/.DLL for:
> >
> /Users/lrosenth/.stack/snapshots/x86_64-osx/a4b9df8230b44b4d1656bd3420d752e1440163e4e9d142f613e0f472365ab993/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHScommonmark-pandoc-0.2.0.0-D01mbkJUemk7h72RuTUjAh-ghc8.6.5.dylib
> >
> (dlopen(/Users/lrosenth/.stack/snapshots/x86_64-osx/a4b9df8230b44b4d1656bd3420d752e1440163e4e9d142f613e0f472365ab993/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHScommonmark-pandoc-0.2.0.0-D01mbkJUemk7h72RuTUjAh-ghc8.6.5.dylib,
> > 5): Symbol not found:
> >
> _pandoczmtypeszm1zi21zmLb7evYKD6jv46JnhbWrkOK_TextziPandocziBuilder_normalizzeTableFootzunormalizzeRowszq_closure
> > Referenced from:
> >
> /Users/lrosenth/.stack/snapshots/x86_64-osx/a4b9df8230b44b4d1656bd3420d752e1440163e4e9d142f613e0f472365ab993/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHScommonmark-pandoc-0.2.0.0-D01mbkJUemk7h72RuTUjAh-ghc8.6.5.dylib
> > Expected in:
> >
> /Users/lrosenth/.stack/snapshots/x86_64-osx/0bf2dc0c6fb03a8a3c3fd1819c92943191347f522011fdc733a961a0bb6b76dc/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHSpandoc-types-1.21-Lb7evYKD6jv46JnhbWrkOK-ghc8.6.5.dylib
> > in
> >
> /Users/lrosenth/.stack/snapshots/x86_64-osx/a4b9df8230b44b4d1656bd3420d752e1440163e4e9d142f613e0f472365ab993/8.6.5/lib/x86_64-osx-ghc-8.6.5/libHScommonmark-pandoc-0.2.0.0-D01mbkJUemk7h72RuTUjAh-ghc8.6.5.dylib)
> >
> > -- While building package pandoc-2.10.1 using:
> >
> >
> /Users/lrosenth/.stack/setup-exe-cache/x86_64-osx/Cabal-simple_mPHDZzAJ_2.4.0.1_ghc-8.6.5
> > --builddir=.stack-work/dist/x86_64-osx/Cabal-2.4.0.1 build lib:pandoc
> > exe:pandoc --ghc-options " -fdiagnostics-color=always"
> >
> > --
> > 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/CALu%3Dv3%2B_gucQ_xOxEO-4%3D5712A1135aSUZNNn1qpuYOmZVBryA%40mail.gmail.com
> .
>
--
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/CALu%3Dv3K%3D%3DwDjAhx1G3YGQMXDgVYe7tOWSvMvz40gYMMXGtRE1w%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 7008 bytes --]
next prev parent reply other threads:[~2020-09-11 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 23:44 Leonard Rosenthol
[not found] ` <CALu=v3+_gucQ_xOxEO-4=5712A1135aSUZNNn1qpuYOmZVBryA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-10 23:50 ` John MacFarlane
[not found] ` <m2imclqji1.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-09-10 23:54 ` Leonard Rosenthol
[not found] ` <CALu=v3J8psTXJbmV62u8eem6+_FZ1qNvSEABJuekARLtnhSOhQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-11 0:01 ` Leonard Rosenthol
2020-09-11 0:03 ` Leonard Rosenthol [this message]
[not found] ` <CALu=v3K==wDjAhx1G3YGQMXDgVYe7tOWSvMvz40gYMMXGtRE1w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-11 0:35 ` Leonard Rosenthol
[not found] ` <CALu=v3LK1TWA3Kod2dA_V0n9me9Sif5aQv0aMKzqkpFTCMV1wQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-11 0:47 ` John MacFarlane
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='CALu=v3K==wDjAhx1G3YGQMXDgVYe7tOWSvMvz40gYMMXGtRE1w@mail.gmail.com' \
--to=leonardr-bm6h3k5um15l57midrcfdg@public.gmane.org \
--cc=jgm-TVLZxgkOlNX2fBVCVOL8/A@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).