unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Brett Gilio <brettg@posteo.net>
Cc: guix-devel@gnu.org, 38605@debbugs.gnu.org
Subject: [bug#38605] [WIP MLton 0/1] Add MLton
Date: Tue, 12 Apr 2022 12:21:50 +0200	[thread overview]
Message-ID: <86h76y38ld.fsf_-_@gmail.com> (raw)
In-Reply-To: <87ft7kqmze.fsf@gmail.com> (zimoun's message of "Mon, 14 Sep 2020 19:36:37 +0200")

Hi,

CC: guix-devel

On Mon, 14 Sep 2020 at 19:36, zimoun <zimon.toutoune@gmail.com> wrote:

> Digging in old unmerged patches, I hit this one. :-)

The last interaction of this WIP patch #38605 [1] about MLton is from 1
year, 29 weeks, 6 days ago.  Whereas the discussion in this thread about
bootstrap strategies is really worth, I am going to close the submission
soon.

1: <http://issues.guix.gnu.org/issue/38605>


> On Fri, 13 Dec 2019 at 21:59, Brett Gilio <brettg@posteo.net> wrote:
>
>> * gnu/packages/sml.scm (mlton-no-gcc): New variable.
>> ---
>>  gnu/packages/sml.scm | 138 +++++++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 138 insertions(+)
>
> What is the status of the WIP?
> Have you make progress?

This patch requires a little rebase and could be included in Guix.

Any taker?


>> diff --git a/gnu/packages/sml.scm b/gnu/packages/sml.scm
>> index 30ee58c498..e45ce4c59c 100644
>> --- a/gnu/packages/sml.scm
>> +++ b/gnu/packages/sml.scm
>> @@ -75,3 +75,141 @@ function interface, and a symbolic debugger.")
>>      (license
>>       (list license:lgpl2.1
>>             license:lgpl2.1+))))
>> +
>> +(define-private mlton-reduced
>> +  (package
>> +   (name "mlton")
>> +   (version "20180207")
>> +   (source (origin
>> +	    (method url-fetch)
>> +	    (uri (string-append "https://github.com/MLton/" name
>> +				"/releases/download/on-" version
>> +				"-release/" name "-" version
>> +				"-1.amd64-linux.tgz"))
>> +	    (sha256
>> +	     (base32
>> +	      "0f4q575yfm5dpg4a2wsnqn4l2zrar96p6rlsk0dw10ggyfwvsjlf"))))
>> +   (build-system trivial-build-system)
>> +   ;; TODO: The build arguments can be much more programmatic.
>> +   (arguments
>> +    '(#:modules
>> +      ((guix build utils))
>> +      #:builder
>> +       (begin
>> +         (use-modules (guix build utils))
>> +         (let*
>> +	     ((out (assoc-ref %outputs "out"))
>> +	      (source (assoc-ref %build-inputs "source"))
>> +	      (tar (string-append (assoc-ref %build-inputs "tar") "/bin/tar"))
>> +	      (patchelf (string-append (assoc-ref %build-inputs "patchelf") "/bin/patchelf"))
>> +	      (ld (string-append (assoc-ref %build-inputs "glibc") "/lib/ld-linux-x86-64.so.2"))
>> +	      (gmp (string-append (assoc-ref %build-inputs "gmp") "/lib"))
>> +	      (bash (string-append (assoc-ref %build-inputs "bash") "/bin/bash"))
>> +	      (rm (string-append (assoc-ref %build-inputs "coreutils") "/bin/rm"))
>> +	      (PATH
>> +	       (string-append
>> +	        (assoc-ref %build-inputs "gzip") "/bin"
>> +	        ":"
>> +	        (assoc-ref %build-inputs "tar") "/bin")))
>> +	   (mkdir-p out)
>> +	   (mkdir-p (string-append out "/bin"))
>> +	   (with-directory-excursion out
>> +				     (setenv "PATH" PATH)
>> +				     (system* tar "xf" source "--strip-components=1")
>> +				     ;; PATCHES FOR /LIB/MLTON/MLTON-COMPILE
>> +				     (system* patchelf
>> +					      "--set-interpreter"
>> +					      ld
>> +					      (string-append out "/lib/mlton/mlton-compile"))
>> +				     (system* patchelf
>> +					      "--set-rpath"
>> +					      gmp
>> +					      (string-append out "/lib/mlton/mlton-compile"))
>> +				     ;; PATCHES FOR /BIN/MLLEX
>> +				     (system* patchelf
>> +					      "--set-interpreter"
>> +					      ld
>> +					      (string-append out "/bin/mllex"))
>> +				     (system* patchelf
>> +					      "--set-rpath"
>> +					      gmp
>> +					      (string-append out "/bin/mllex"))
>> +				     ;; PATCHES FOR /BIN/MLYACC
>> +				     (system* patchelf
>> +					      "--set-interpreter"
>> +					      ld
>> +					      (string-append out "/bin/mlyacc"))
>> +				     (system* patchelf
>> +					      "--set-rpath"
>> +					      gmp
>> +					      (string-append out "/bin/mlyacc"))
>> +				     ;; DELETE ALL UNNEEDED COMPONENTS
>> +				     (system* rm "-rf"
>> +					      "bin/mlprof"
>> +					      "bin/mlnlffigen"
>> +					      "LICENSE"
>> +					      "Makefile"
>> +					      "CHANGELOG.adoc"
>> +					      "README.adoc"
>> +					      "share")
>> +				     ;; PATCH SHEBANG FOR BIN/MLTON
>> +				     (substitute* "bin/mlton"
>> +						  (("/usr/bin/env bash")
>> +						   bash)))))))
>> +   (native-inputs `(("glibc" ,glibc)
>> +		    ("patchelf" ,patchelf)
>> +		    ("tar" ,tar)
>> +		    ("bash" ,bash)
>> +		    ("coreutils" ,coreutils)
>> +		    ("gzip" ,gzip)
>> +		    ("gmp" ,gmp)))
>> +   (supported-systems '("x86_64-linux"))
>> +   (synopsis #f)
>> +   (description #f)
>> +   (home-page #f)
>> +   (license #f)))
>> +
>> +(define-public mlton-no-gcc
>> +  (package
>> +   (name "mlton-no-gcc")
>> +   (version "20180207")
>> +   (source (origin
>> +	    (method url-fetch)
>> +	    (uri (string-append "https://github.com/MLton/" name
>> +				"/archive/on-" version
>> +				"-release.tar.gz"))
>> +	    (sha256
>> +	     (base32
>> +	      "1l1flhxx8hr4n3mf87m02231r3m2f3sh28zfxma3g41jscmj21zi"))))
>> +   (build-system gnu-build-system)
>> +   (arguments
>> +    `(#:parallel-build? #f ; See: https://github.com/MLton/mlton/issues/348
>> +      #:phases
>> +      (modify-phases %standard-phases
>> +		     (delete 'configure)
>> +		     (replace 'install
>> +			      (lambda _
>> +				(invoke "make"
>> +					(string-append "PREFIX=" (assoc-ref %outputs "out"))
>> +					"install"))))))
>> +   (native-inputs
>> +    `(("mlton" ,mlton-reduced)
>> +      ("which" ,which)))
>> +   (propagated-inputs
>> +    `(("gmp" ,gmp)))
>> +   (supported-systems '("x86_64-linux"))
>> +   (synopsis "Whole-program, optimizing Standard ML compiler")
>> +   (description "MLton is a whole-program optimizing compiler for Standard ML.
>> +MLton generates standalone executables with excellent runtime performance, is
>> +SML '97 compliant, and has a complete basis library. MLton has source-level
>> +profiling, a fast C FFI, an interface to the GNU multiprecision library, and
>> +lots of useful libraries.")
>> +   (home-page "http://mlton.org/")
>> +   (license license:hpnd)))
>> +
>> +(define-public mlton
>> +  (package (inherit mlton-no-gcc)
>> +	   (name "mlton")
>> +	   (propagated-inputs
>> +	    `(("gcc-toolchain" ,gcc-toolchain)
>> +	      ,@(package-propagated-inputs mlton-no-gcc)))))


Cheers,
simon




  reply	other threads:[~2022-04-12 10:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14  3:58 [bug#38605] [WIP MLton 0/1] Add MLton Brett Gilio
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     ` zimoun [this message]
2022-05-04 11:58       ` bug#38605: [WIP MLton 0/1] Add MLton 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=86h76y38ld.fsf_-_@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=38605@debbugs.gnu.org \
    --cc=brettg@posteo.net \
    --cc=guix-devel@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).