public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: Tom Tromey <tom@tromey.com>, Andrew Hughes <gnu.andrew@redhat.com>
Cc: Jeff Law <law@redhat.com>, Uros Bizjak <ubizjak@gmail.com>,
	       gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org,
	       Andrew Haley <aph@redhat.com>
Subject: Re: [PATCH, libjava/classpath]: Fix overriding recipe for target 'gjdoc' build warning
Date: Thu, 20 Aug 2015 08:24:00 -0000	[thread overview]
Message-ID: <55D58ED0.1020402@ubuntu.com> (raw)
In-Reply-To: <87y4h68tk3.fsf@tromey.com>

On 08/20/2015 06:36 AM, Tom Tromey wrote:
> Andrew> No, it isn't. It's still a necessity for initial bootstrapping of
> Andrew> OpenJDK/IcedTea.
> 
> Andrew Haley said the opposite here:
> 
> https://gcc.gnu.org/ml/gcc-patches/2015-08/msg00537.html

if you need bootstrapping OpenJDK 6 or OpenJDK 7, then having gcj available for
the target platform is required. Starting with OpenJDK 8 you should be able to
cross build OpenJDK 8 with an OpenJDK 8 available on the cross platform.  It
might be possible to cross build older OpenJDK versions, but this usually is
painful.

Matthias

  reply	other threads:[~2015-08-20  8:24 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 11:22 Uros Bizjak
2015-08-11 18:03 ` Uros Bizjak
2015-08-11 18:54   ` Jeff Law
2015-08-11 19:24     ` Andrew Haley
2015-08-11 19:34       ` Jeff Law
2015-08-12  2:48     ` Tom Tromey
2015-08-12 14:44       ` Jeff Law
2015-08-12 14:57         ` Andrew Haley
2015-08-12 16:23           ` Ian Lance Taylor
2015-08-12 16:21         ` Tom Tromey
2015-08-12 16:24           ` Ian Lance Taylor
2015-08-12 16:47             ` Jeff Law
2015-08-12 16:59               ` Ian Lance Taylor
2015-08-13 10:00               ` Richard Biener
2015-08-13 21:31                 ` Jeff Law
2015-08-14  7:44                   ` Richard Biener
2015-08-14  9:24                     ` Andrew Haley
2015-08-20  2:35       ` Andrew Hughes
2015-08-20  4:37         ` Tom Tromey
2015-08-20  8:24           ` Matthias Klose [this message]
2015-08-20  8:32             ` Andrew Haley
2015-08-20 14:57               ` Andrew Hughes
2015-08-20 15:27                 ` Andrew Haley
2015-08-20 15:47                   ` Jeff Law
2015-08-20 16:03                     ` Andrew Hughes
2015-08-20 16:08                       ` Andrew Haley
2015-08-20 16:26                         ` Andrew Hughes
2015-08-20 16:38                         ` Richard Biener
2015-08-20 16:39                           ` Andrew Haley
2015-08-20 17:35                       ` Jeff Law
2015-08-20 17:39                         ` Andrew Hughes
2015-08-20 15:52                   ` Andrew Hughes
2015-08-20 16:34                     ` Richard Biener
2015-08-20 16:59                       ` Andrew Hughes
2015-08-20 17:35                         ` Andrew Hughes
2015-08-20 18:05                           ` Richard Biener
2015-08-20 21:06                             ` Joseph Myers
2015-08-20 22:32                             ` Andrew Hughes
2015-08-24 16:39                               ` Jeff Law
2015-08-20 14:58           ` Andrew Hughes
2015-08-20  2:48   ` Andrew Hughes
2015-08-20  6:20     ` Uros Bizjak

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=55D58ED0.1020402@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=aph@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu.andrew@redhat.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=tom@tromey.com \
    --cc=ubizjak@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).