From: Luis Rivera <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: tiny core linux
Date: Mon, 12 Aug 2019 09:02:16 -0700 (PDT) [thread overview]
Message-ID: <46d08490-070d-4a14-81d0-181ee3c0d1ce@googlegroups.com> (raw)
In-Reply-To: <CAJTYOd1xd=ny896Y2s=2Ofa-BokL27mB=assUNRd=ToR_udLNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 955 bytes --]
On Thursday, 1 August 2019 02:27:50 UTC-5, latk wrote:
>
> Pandoc doesn't require special hardware. The normal Pandoc binaries should
> work.
>
I am unhappy to report that, apparently, it does. The distributed Linux
binaries work on x86_64 machines, even under Tiny Core, but don't on ARM or
i386 hardware, under emulation on qemu.
I don't know how to post a request for 32 bit Linux binaries, the same way
that there are Win32 and Win64 binaries in the distro. I don't use Macs, so
I don't know what's the situation there.
Cheers,
--
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/46d08490-070d-4a14-81d0-181ee3c0d1ce%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1523 bytes --]
next prev parent reply other threads:[~2019-08-12 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 1:10 Luis Rivera
[not found] ` <cec28252-af6f-4ad0-a157-1fd624a9b148-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-01 7:27 ` Lukas Atkinson
[not found] ` <CAJTYOd1xd=ny896Y2s=2Ofa-BokL27mB=assUNRd=ToR_udLNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-12 16:02 ` Luis Rivera [this message]
[not found] ` <46d08490-070d-4a14-81d0-181ee3c0d1ce-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-12 16:26 ` BPJ
[not found] ` <CADAJKhBjRYNj8VxhpRugBm_VvkrHMc9UGRxUW__OFJwJmU3nyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-12 20:14 ` Luis Rivera
[not found] ` <5fd3251e-d88b-4f40-a71f-e0e65c73ee24-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-12 22:46 ` John MacFarlane
[not found] ` <yh480ko90uknne.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-15 19:01 ` Luis Rivera
[not found] ` <f0b39d62-808a-4ae9-84ae-4fd41ea03c6f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-06 23:39 ` Luis Rivera
[not found] ` <71ee5649-ca62-4f89-a3b5-1f2d48459810-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-07 0:57 ` EBkysko
2020-05-07 1:00 ` EBkysko
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=46d08490-070d-4a14-81d0-181ee3c0d1ce@googlegroups.com \
--to=jlrn77-re5jqeeqqe8avxtiumwx3w@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).