unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Ricardo Wurmus <rekado@elephly.net>,
	Leo Prikler <leo.prikler@student.tugraz.at>
Cc: guix-devel@gnu.org
Subject: Re: Scala package
Date: Tue, 18 May 2021 07:15:56 -0400	[thread overview]
Message-ID: <E9CBAA1B-1155-4D66-A29B-DC78A613FE81@lepiller.eu> (raw)
In-Reply-To: <875yzgjrzp.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 2689 bytes --]

The old scala is written in a superset of java5, that requires PiCo to build, and PiCo was built with JaCo. They were developped at EPFL, and you can find a binary for it, but no source: http://zenger.org/jaco/

Apparently, JaCo was later reimplemented in Keris, whose source code is available. However, KeCo (the Keris compiler) is written in Keris.

It is not even clear that building an old version of scala is going to work, as the language evolved a lot since then.

I think the best way to bootstrap would be to reimplement Scala in another language. I tried that too, but even the parser is crazy.

Le 18 mai 2021 05:44:42 GMT-04:00, Ricardo Wurmus <rekado@elephly.net> a écrit :
>
>Leo Prikler <leo.prikler@student.tugraz.at> writes:
>
>> Hi Julien,
>>
>> Am Dienstag, den 18.05.2021, 01:01 +0200 schrieb Julien 
>> Lepiller:
>>> Hi Guix!
>>> 
>>> I have the attached file that build Scala, although it's not
>>> bootstrapped at all. It contains %binary-scala, a few 
>>> dependencies of
>>> Scala we haven't packaged yet, and the final scala, built from
>>> %binary-scala, without sbt (which requires Scala too).
>>> 
>>> Since I've tried and failed to bootstrap Scala for so long, I 
>>> think
>>> it's time to give up. I can't always create miracles.
>>
>> Some points relevant to bootstrapping:
>> - The last version, that ships "scalai" written in Java seems to 
>> be 
>>   v1.4.0+4.  Perhaps one can use scalai to bootstrap scalac 
>>   within it.
>> - The last version, that does not "require" sbt is 2.11.x,
>>   though with your workaround we can also build later versions.
>
>We tried building a clean bootstrap chain for Scala for years. 
>Back then I went down the rabbit hole and found that early scalac 
>is written in Pizza; but it turned out that Pizza is written in 
>Pizza and is released under the old Artistic License, which is 
>considered non-free.
>
>    https://logs.guix.gnu.org/guix/2018-04-08.log#230002
>    https://logs.guix.gnu.org/guix/2018-04-09.log#073740
>
>I pointed a branch at an old Scala commit that contains the old 
>Socos compiler source, which ostensibly are written in Java, but 
>actually are not:
>
>    https://github.com/rekado/scala-bootstrap/tree/bootstrap
>
>This is at around version 1.4.0.4, as you wrote above.
>
>Since the old days Scala Native has grown considerably, and 
>perhaps we can reuse some of its native libraries.  I’m not too 
>hopeful, because the bulk of it is still written in Scala, 
>obviously, but there are parts that are written in C / C++, which 
>might come in handy.
>
>    https://github.com/scala-native/scala-native
>
>-- 
>Ricardo

[-- Attachment #2: Type: text/html, Size: 3506 bytes --]

  reply	other threads:[~2021-05-18 11:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 23:01 Scala package Julien Lepiller
2021-05-18  7:08 ` Leo Prikler
2021-05-18  9:44   ` Ricardo Wurmus
2021-05-18 11:15     ` Julien Lepiller [this message]
2021-05-18 11:36       ` Leo Prikler
2021-05-18 12:37         ` Julien Lepiller
2021-05-18 13:52           ` Leo Prikler
2021-05-18 21:35       ` Ludovic Courtès
2021-05-19 15:35         ` Katherine Cox-Buday
2021-05-20 19:09           ` Shyam Saran
2021-05-20 19:34             ` Julien Lepiller
2021-05-21  9:32               ` Shyam Saran
2021-05-18 14:00     ` Daniel Trujillo Viedma

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=E9CBAA1B-1155-4D66-A29B-DC78A613FE81@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=rekado@elephly.net \
    /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).