From: Ricardo Wurmus <rekado@elephly.net>
To: zloster <more@edno.moe>
Cc: help-guix@gnu.org, Zachary Kanfer <zkanfer@gmail.com>
Subject: Re: After installing Java, what should I set JAVA_HOME to?
Date: Thu, 01 Dec 2016 09:59:32 +0100 [thread overview]
Message-ID: <874m2odnyj.fsf@elephly.net> (raw)
In-Reply-To: <20c1854d-01a1-b6d1-5690-6265e02e513f@edno.moe>
zloster <more@edno.moe> writes:
> There is icedtea-3.1.0
That’s the problem: icedtea 3.1.0 cannot build the keystore, which is
why this build phase has been removed.
IcedTea (the free software build system for OpenJDK) doesn’t come with a
keystore by default and doesn’t try to generate it, so what we do in
Guix is to add a build phase in which a “cacerts” file is built from the
NSS certificate store and saved to “$jdk/jre/lib/security” and
“$jre/lib/security”.
For 3.1.0 this phase fails for unknown reasons, so I removed it. This
means that 3.1.0 doesn’t have SSL support out of the box. The two
previous versions however do, so if you want to avoid custom hacks I
encourage you to install 2.6.7:
guix package -i icedtea@2.6
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
http://elephly.net
next prev parent reply other threads:[~2016-12-01 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 4:38 After installing Java, what should I set JAVA_HOME to? Zachary Kanfer
2016-11-02 6:18 ` Chris Marusich
2016-11-08 4:20 ` Zachary Kanfer
2016-11-08 12:31 ` Ludovic Courtès
2016-11-08 15:15 ` Ricardo Wurmus
2016-11-09 7:01 ` Chris Marusich
2016-11-09 21:22 ` Hartmut Goebel
2016-11-28 5:15 ` Zachary Kanfer
2016-11-28 8:45 ` Ricardo Wurmus
2016-11-30 22:01 ` zloster
2016-12-01 8:59 ` Ricardo Wurmus [this message]
2016-11-28 9:59 ` Ludovic Courtès
2016-11-28 17:08 ` Hartmut Goebel
2016-11-29 2:34 ` Chris Marusich
2016-11-08 15:13 ` Ricardo Wurmus
-- strict thread matches above, loose matches on Subject: below --
2016-11-12 18:48 Radoslav Petrov
2016-12-01 2:18 ` Chris Marusich
2016-12-01 13:06 ` Ludovic Courtès
2016-12-01 13:07 ` 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
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=874m2odnyj.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=more@edno.moe \
--cc=zkanfer@gmail.com \
/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.
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).