public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Anthony Green <green@redhat.com>
To: bill.chatfield@yahoo.com, Bill Chatfield <bill_chatfield@yahoo.com>
Cc: Ricardo Wurmus <rekado@elephly.net>,
	Andrew Haley <aph@redhat.com>, mohan NMH <mohan.nmh2@gmail.com>,
		java@gcc.gnu.org
Subject: Re: Fwd: gcj can not import packages
Date: Mon, 16 Jan 2017 23:24:00 -0000	[thread overview]
Message-ID: <CAAs=kogWDGGzYBpyThUWO9rwXWGoXr-Oy0P3UUiDyS5kjOHuYQ@mail.gmail.com> (raw)
In-Reply-To: <59dc01d2704c$0d4ea910$27ebfb30$@yahoo.com>

This is an interesting question... For the extremely security
conscious, how can we build OpenJDK from source, assuming we have no
trusted JDK?  Can something simpler than gcj be used, like kaffe?

AG

On Mon, Jan 16, 2017 at 5:58 PM, Bill Chatfield via java
<java@gcc.gnu.org> wrote:
> From the link, it looks like it would be correct to say that gcj is the *only* open source way to bootstrap OpenJDK.
>
> -----Original Message-----
> From: Ricardo Wurmus [mailto:rekado@elephly.net]
> Sent: Monday, January 16, 2017 3:10 PM
> To: Bill Chatfield <bill_chatfield@yahoo.com>
> Cc: 'Andrew Haley' <aph@redhat.com>; 'mohan NMH' <mohan.nmh2@gmail.com>; java@gcc.gnu.org
> Subject: Re: Fwd: gcj can not import packages
>
>
> Bill Chatfield via java <java@gcc.gnu.org> writes:
>
>> I understand that OpenJDK is available as open source now, to
>> "replace" gcj. But, gcj still has certain advantages that OpenJDK does
>> not have:
>>
>> 1. gcj can compile to a native executable. […]
>>
>> 2 gij is more memory efficient than OpenJDK at runtime. […]
>>
>> 3. OpenJDK only supports a few platforms. […]
>
> I would like to add one point: GCJ can be used to cleanly bootstrap the OpenJDK from source with a chain that starts with GCC’s C compiler, to GCJ, to OpenJDK 6 (via IcedTea).
>
> (The only wart is that later versions of GCJ rely on a pre-built jar of
> ecj.)
>
> This is why the bootstrappable builds project lists “Maintaining the GNU Compiler for Java” as a collaboration project.[1]
>
> [1]: http://bootstrappable.org/projects.html
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC https://elephly.net
>
>

  reply	other threads:[~2017-01-16 23:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANV4OqjehvrZUaMGbwn0Gu3KsesTy7aWVhY9cPETpnqwf_Zo0A@mail.gmail.com>
2016-11-09 11:29 ` mohan NMH
2016-11-09 12:26   ` Andrew Haley
2016-11-09 12:49     ` mohan NMH
2016-11-09 13:29       ` Andrew Haley
2017-01-16 17:41         ` Bill Chatfield via java
2017-01-16 20:10           ` Ricardo Wurmus
2017-01-16 22:58             ` Bill Chatfield via java
2017-01-16 23:24               ` Anthony Green [this message]
2017-01-17  9:56               ` Andrew Haley
2017-01-18 20:29                 ` Ricardo Wurmus
2017-01-18 20:40                   ` Matthias Klose
2017-01-18 20:59                     ` Ricardo Wurmus
2017-01-19  9:59                       ` Andrew Haley
     [not found]                         ` <CAFXTvn525N1D_EOuCAWXSJugCpZCZCkc5GfuhNJ1nPoDK0DAoQ@mail.gmail.com>
2017-05-17 20:26                           ` Ricardo Wurmus
2017-01-17  9:58           ` Andrew Haley
2017-01-17 15:21             ` Bill Chatfield via java

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='CAAs=kogWDGGzYBpyThUWO9rwXWGoXr-Oy0P3UUiDyS5kjOHuYQ@mail.gmail.com' \
    --to=green@redhat.com \
    --cc=aph@redhat.com \
    --cc=bill.chatfield@yahoo.com \
    --cc=bill_chatfield@yahoo.com \
    --cc=java@gcc.gnu.org \
    --cc=mohan.nmh2@gmail.com \
    --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.
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).