From: Luis Rivera <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: tiny core linux
Date: Wed, 6 May 2020 16:39:54 -0700 (PDT) [thread overview]
Message-ID: <71ee5649-ca62-4f89-a3b5-1f2d48459810@googlegroups.com> (raw)
In-Reply-To: <f0b39d62-808a-4ae9-84ae-4fd41ea03c6f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1601 bytes --]
Well: I fear this workaround does not work anymore: the wine library is a
few steps behind windows development, and the new win architecture is not
fully supported.
So, should I ask for a Linux static build for 32 bits?
Sincerely,
Luis
On Thursday, 15 August 2019 14:01:10 UTC-5, Luis Rivera wrote:
>
>
>
> On Monday, 12 August 2019 17:46:44 UTC-5, John MacFarlane wrote:
>>
>>
>> You can always spin up a build machine in the cloud, with more
>> resources, and then use the resulting binary on your tiny machine.
>>
>>
> I fear I don't know how to do that; in fact, once I tried to compile
> pandoc on my own, and found the whole cabal/ghc incantation overwhelming (I
> am no hacker, only and advanced luser).
>
> However, I am happy to report that, after some sort of inspiration, it
> occurred to me that I didn't have to run the qemu emulator to execute the
> Linux x86_64 executable on the 32 bit system and machine, if I could run
> the Windoze 32 bit executable under `wine` (n.b. a compatibility layer, not
> an emulator) on the Tiny Core 32 / Intelx86_32 machine. And it worked (at
> least so far)!
>
> I'm leaving this crumb for others to pick up.
>
> 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/71ee5649-ca62-4f89-a3b5-1f2d48459810%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2347 bytes --]
next prev parent reply other threads:[~2020-05-06 23:39 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
[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 [this message]
[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=71ee5649-ca62-4f89-a3b5-1f2d48459810@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).