From: thomas.hodgson-6DaNJ7gwbyQ@public.gmane.org
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc-citeproc with pandoc 2
Date: Tue, 31 Oct 2017 04:37:40 -0700 (PDT) [thread overview]
Message-ID: <1fdfd4b1-217f-42dc-bb42-012a54504122@googlegroups.com> (raw)
In-Reply-To: <20171030233029.GA63834@protagoras>
[-- Attachment #1.1: Type: text/plain, Size: 4103 bytes --]
Yes, it's fixed. Thank you.
And thank you for all your work on version 2.
On Monday, 30 October 2017 23:31:12 UTC, John MacFarlane wrote:
>
> OK, try the new deb I've put on the release page (revision 3).
> I think it fixes this issue.
>
> +++ John MACFARLANE [Oct 30 17 14:15 ]:
> >I see the issue:
> >
> >ldd /usr/bin/pandoc-citeproc
> > linux-vdso.so.1 (0x00007fffee74e000)
> > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fb8f4f3b000)
> > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10
> (0x00007fb8f4cb8000)
> > libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6
> (0x00007fb8f4aaf000)
> > libc.musl-x86_64.so.1 => not found
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb8f4710000)
> > /lib/ld-musl-x86_64.so.1 => /lib64/ld-linux-x86-64.so.2
> (0x00007fb8f5155000)
> >
> >I guess the build process didn't set the flags correctly
> >for a static build of pandoc-citeproc (only pandoc).
> >I'll see if I can fix this.
> >
> >
> >+++ thomas....-6DaNJ7gwbyQ@public.gmane.org <javascript:> [Oct 30 17 12:00 ]:
> >> I've just installed pandoc 2 with the latest .deb package:
> >> https://github.com/jgm/pandoc/releases/download/2.0/pandoc-2.0-2-amd64.
>
> >> deb
> >> I now get this error when I try to convert Markdown to PDF with `$
> >> pandoc --bibliography=foo.bib --output foo.pdf foo.md`:
> >> ```
> >> Error running filter pandoc-citeproc:
> >> pandoc-citeproc: createProcess: runInteractiveProcess: exec: does not
> >> exist (No such file or directory)
> >> ```
> >> A bit of looking around suggests that one explanation might be that
> the
> >> package didn't install the latest version of pandoc-citeproc. It
> should
> >> have done, right? What's the easiest way for me to get a working
> >> pandoc-citeproc?
> >>
> >> --
> >> 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
> >> To post to this group, send email to
> >> [2]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
> >> To view this discussion on the web visit
> >> [3]
> https://groups.google.com/d/msgid/pandoc-discuss/903525e9-a094-42e8-
> >> b764-bd786b685661%40googlegroups.com.
> >> For more options, visit [4]https://groups.google.com/d/optout.
> >>
> >>References
> >>
> >> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>
> >> 2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>
> >> 3.
> https://groups.google.com/d/msgid/pandoc-discuss/903525e9-a094-42e8-b764-bd786b685661-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> >> 4. https://groups.google.com/d/optout
> >
> >--
> >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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
> >To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> <javascript:>.
> >To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/20171030211532.GB56096%40protagoras.
>
> >For more options, visit https://groups.google.com/d/optout.
>
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/1fdfd4b1-217f-42dc-bb42-012a54504122%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 438496 bytes --]
prev parent reply other threads:[~2017-10-31 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 19:00 thomas.hodgson-6DaNJ7gwbyQ
[not found] ` <903525e9-a094-42e8-b764-bd786b685661-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-30 21:15 ` John MACFARLANE
2017-10-30 23:30 ` John MACFARLANE
2017-10-31 11:37 ` thomas.hodgson-6DaNJ7gwbyQ [this message]
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=1fdfd4b1-217f-42dc-bb42-012a54504122@googlegroups.com \
--to=thomas.hodgson-6danj7gwbyq@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).