From: A jeep <ajeep8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: My build executable file very larger then release
Date: Mon, 30 May 2022 22:18:42 -0700 (PDT) [thread overview]
Message-ID: <5e412d02-44fd-4ce5-947e-9872cb918c1cn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
I'm not familiar with Haskell.
In my utuntu 20.04, I `stack install pandoc pandoc-crossref`, the result
exec files are very larger then official release:
```
179924840 pandoc
125288616 pandoc-crossref
```
And I try to use Haskell docker:
```
docker run -it --rm --entrypoint=/bin/sh haskell:8.10
cabal update
cabal install pandoc pandoc-crossref
```
the results are more larger then the former.
How can I shrink the exec files to pandoc official release file size?
--
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/5e412d02-44fd-4ce5-947e-9872cb918c1cn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1413 bytes --]
next reply other threads:[~2022-05-31 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 5:18 A jeep [this message]
[not found] ` <5e412d02-44fd-4ce5-947e-9872cb918c1cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-31 6:18 ` Albert Krewinkel
[not found] ` <871qwa6x1n.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-05-31 20:16 ` John MacFarlane
[not found] ` <m25yllzcdr.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-01 7:05 ` A jeep
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=5e412d02-44fd-4ce5-947e-9872cb918c1cn@googlegroups.com \
--to=ajeep8-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).