public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Interested in pre-built pandoc binary for Raspberry Pi?
Date: Sun, 24 Nov 2019 21:08:24 -0800 (PST)	[thread overview]
Message-ID: <f7812845-5e9c-4acb-b251-425a4c0dfaaf@googlegroups.com> (raw)
In-Reply-To: <b6e39060-b59f-4a5d-a57e-ca757671439a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1581 bytes --]

Interestingly, as I was trying to compile pandoc 2.8 on Raspberry Pi 4 I 
encountered the following error:

[129 of 157] Compiling Text.Pandoc.Readers.LaTeX

ghc: internal error: getMBlock: mmap: Invalid argument

    (GHC version 8.4.4 for arm_unknown_linux)

    Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

cabal: Leaving directory '/tmp/cabal-tmp-4329/pandoc-2.8'

cabal: Error: some packages failed to install:

pandoc-2.8-7DuyvaKAuuG7FMyA94fihL failed during the building phase. The

exception was:

ExitFailure (-6)

So it seems to be compiler bug very similar 
to https://gitlab.haskell.org/ghc/ghc/issues/16383

But looking at https://gitlab.haskell.org/ghc/ghc/issues/7500 it seems this 
error can be related to insufficient memory?

I checked and the memory used is Maximum resident set size (kbytes): 2963812

And from https://www.raspberrypi.org/forums/viewtopic.php?t=244367 the max 
amount of memory per process is 3GiB on 32bit Linux as 1GB virtual memory 
is locked.

IIRC, pandoc 2.7.3 compiles using around 2.8 GiB. So pandoc 2.8 seems to 
require more memory to compile. I wonder if the same problem is seen in 
Linux x86.

-- 
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/f7812845-5e9c-4acb-b251-425a4c0dfaaf%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 4398 bytes --]

      parent reply	other threads:[~2019-11-25  5:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 10:13 Kolen Cheung
     [not found] ` <0261ce84-ce3e-4d0e-bc54-8ffc57426ed3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-19 18:30   ` John MacFarlane
     [not found]     ` <yh480kpnjwf89o.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-20  7:45       ` mb21
     [not found]         ` <b6e39060-b59f-4a5d-a57e-ca757671439a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-11-25  5:08           ` Kolen Cheung [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=f7812845-5e9c-4acb-b251-425a4c0dfaaf@googlegroups.com \
    --to=christian.kolen-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).