From: Brett Gilio <brettg@posteo.net>
To: 38605@debbugs.gnu.org
Subject: [bug#38605] [WIP MLton 0/1] Add MLton
Date: Fri, 13 Dec 2019 21:58:10 -0600 [thread overview]
Message-ID: <877e2z7e3x.fsf@posteo.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: [WIP MLton 0/1] Add MLton --]
[-- Type: text/x-patch, Size: 851 bytes --]
From d6e94b0a04bf71e51d29b7228bd4233bf763eaaa Mon Sep 17 00:00:00 2001
From: Brett Gilio <brettg@posteo.net>
Date: Fri, 13 Dec 2019 21:54:59 -0600
Subject: [WIP MLton 0/1] Add MLton
MLton is a little bit tricker to package properly as it runs in to the issue
of requiring a non-source, pre-compiled bootstrap. There is a way to get it to
build against SMLnj though (which will be my next WIP bug report). This patch
series uses a series of patched ELFs to compile MLton from source. But obviously
this will not be permissable upstream.
As such I wanted to share my WIP on this for anybody who has any ideas and
so I can keep track of my own progress.
Please send revisions by re-rolling n+1.
Brett Gilio (1):
gnu: Add mlton.
gnu/packages/sml.scm | 138 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 138 insertions(+)
--
2.24.1
next reply other threads:[~2019-12-14 3:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 3:58 Brett Gilio [this message]
2019-12-14 3:59 ` [bug#38605] [WIP MLton 1/1] gnu: Add mlton Brett Gilio
2020-09-14 17:36 ` zimoun
2022-04-12 10:21 ` [bug#38605] [WIP MLton 0/1] Add MLton zimoun
2022-05-04 11:58 ` bug#38605: " zimoun
2019-12-14 17:58 ` [bug#38605] " Ludovic Courtès
2019-12-15 22:32 ` Brett Gilio
2019-12-16 10:02 ` Ludovic Courtès
2019-12-15 1:59 ` zimoun
2019-12-16 21:23 ` Ludovic Courtès
2019-12-17 2:20 ` Brett Gilio
2019-12-17 16:42 ` zimoun
2019-12-18 14:48 ` Ludovic Courtès
2019-12-21 4:56 ` Brett Gilio
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=877e2z7e3x.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=38605@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).