From: Efraim Flashner <efraim@flashner.co.il>
To: 52462@debbugs.gnu.org
Subject: bug#52462: track ocaml support on different architectures
Date: Mon, 13 Dec 2021 11:16:59 +0200 [thread overview]
Message-ID: <YbcPixD5qBnWnRTx@3900XT> (raw)
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
It seems worth it to open a bug to track the current support of camlboot
on different architectures.
x86_64-linux supported (with substitutes)
i686-linux supported (with substitutes)
aarch64-linux unknown
armhf-linux unknown
powerpc64le-linux unknown
I test built camlboot on my aarch64-linux board, it stopped compilation
at ~55 hours with Signal 9 (OOM). 2GB RAM, 2GB swap.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2021-12-13 9:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YbcPixD5qBnWnRTx@3900XT \
--to=efraim@flashner.co.il \
--cc=52462@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).