From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: OpenJDK support
Date: Mon, 8 Feb 2016 15:10:18 +0100 [thread overview]
Message-ID: <idj7fif8f91.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <20160208135740.GA27375@thebird.nl>
Pjotr Prins <pjotr.public12@thebird.nl> writes:
> To support the JVM we'll need to add the openjdk.
>
> Having a look at it I think it is doable. Only problem is that the
> java compiler needs to be bootstrapped with itself.
>
> In Nix they create a binary blob to bootstrap:
>
> let
> # !!! These should be on nixos.org
> src = if glibc.system == "x86_64-linux" then
> fetchurl {
> url = http://tarballs.nixos.org/openjdk-bootstrap-x86_64-linux-2012-08-2
> 4.tar.xz;
> sha256 = "0gla9dxrfq2w1hvgsnn8jg8a60k27im6z43a6iidi0qmwa0wah32";
> }
> else if glibc.system == "i686-linux" then
> fetchurl {
> url = http://tarballs.nixos.org/openjdk-bootstrap-i686-linux-2012-08-24.
> tar.xz;
> sha256 = "184wq212bycwbbq4ix8cc6jwjxkrqw9b01zb86q95kqpa8zy5206";
> }
> else throw "No bootstrap for system";
> in
>
> How do we go about this one?
We already have a JDK provided by the “jdk” output of the “icedtea”
packages. “IcedTea” is the name of the project that provides a heavily
patched framework allowing us to build the (patched) OpenJDK sources
with free software only. Building the vanilla OpenJDK appparently isn’t
that easy – and not really necessary since we have the IcedTea-ified
version.
We are bootstrapping with GCJ.
~~ Ricardo
next prev parent reply other threads:[~2016-02-08 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 13:57 OpenJDK support Pjotr Prins
2016-02-08 14:10 ` Ricardo Wurmus [this message]
2016-02-08 15:22 ` Ludovic Courtès
2016-02-08 16:26 ` Pjotr Prins
2016-02-08 17:26 ` Ricardo Wurmus
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=idj7fif8f91.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.