From: Matthias Klose <doko@ubuntu.com>
To: Ricardo Wurmus <rekado@elephly.net>, Andrew Haley <aph@redhat.com>
Cc: bill.chatfield@yahoo.com, "'mohan NMH'" <mohan.nmh2@gmail.com>,
java@gcc.gnu.org
Subject: Re: Fwd: gcj can not import packages
Date: Wed, 18 Jan 2017 20:40:00 -0000 [thread overview]
Message-ID: <92b25477-ed9d-f35e-a9b4-2cb90e425cbd@ubuntu.com> (raw)
In-Reply-To: <878tq86rjx.fsf@elephly.net>
On 18.01.2017 21:28, Ricardo Wurmus wrote:
>
> Andrew Haley <aph@redhat.com> writes:
>
>> On 16/01/17 22:58, Bill Chatfield via java wrote:
>>
>>> From the link, it looks like it would be correct to say that gcj is
>>> the *only* open source way to bootstrap OpenJDK.
>>
>> OpenJDK can bootstrap itself.
>
> It can bootstrap only with pre-built binaries, though. The only route
> that doesn’t involve these binaries is by using GCJ.
>
> I would be happy to be shown that this is a misunderstanding.
yes, you need some trusted binaries. For example, there are various Linux
distributions which provide these binaries. And even if you want to build for a
target that doesn't have binaries, you can first build a native openjdk on your
build platform, and then cross-build for your target. I built several Linux
architectures this way ...
Matthias
next prev parent reply other threads:[~2017-01-18 20:40 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
2017-01-17 9:56 ` Andrew Haley
2017-01-18 20:29 ` Ricardo Wurmus
2017-01-18 20:40 ` Matthias Klose [this message]
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=92b25477-ed9d-f35e-a9b4-2cb90e425cbd@ubuntu.com \
--to=doko@ubuntu.com \
--cc=aph@redhat.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).