From: David Daney <ddaney@caviumnetworks.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Joern Rennecke <joern.rennecke@embecosm.com>,
Geert Bosch <bosch@adacore.com>,
Steven Bosscher <stevenb.gcc@gmail.com>,
gcc@gcc.gnu.org, java@gcc.gnu.org,
Ian Lance Taylor <iant@google.com>
Subject: Re: PATCH RFA: Do not build java by default
Date: Tue, 02 Nov 2010 16:43:00 -0000 [thread overview]
Message-ID: <4CD03FAF.1070808@caviumnetworks.com> (raw)
In-Reply-To: <4CCFEC80.8050809@gnu.org>
On 11/02/2010 03:48 AM, Paolo Bonzini wrote:
> On 11/01/2010 11:47 AM, Joern Rennecke wrote:
>> Quoting Geert Bosch <bosch@adacore.com>:
>>
>>> On Nov 1, 2010, at 00:30, Joern Rennecke wrote:
>>>> But to get that coverage, testers will need to have gnat installed.
>>>> Will that become a requirement for middle-end patch regression testing?
>>>
>>> No, the language will only be built if a suitable bootstrap compiler
>>> is present.
>>
>> I know that. My question was aimed at soliciting opinions on patch
>> submission policy in the case that libjava build & testing are dropped
>> from standard bootstrap tests.
>
> You already need to have ecj installed, so it's one dependency more and
> one less.
I may be mistaken, but I don't think that is true. Building and testing
of libgcj *does not* require ecj.
David Daney
next prev parent reply other threads:[~2010-11-02 16:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 19:33 Steven Bosscher
2010-10-31 19:47 ` Gerald Pfeifer
2010-11-01 3:48 ` Andrew Pinski
2010-11-01 10:11 ` Dave Korn
2010-11-01 4:06 ` Geert Bosch
2010-11-01 4:30 ` Joern Rennecke
2010-11-01 10:35 ` Geert Bosch
2010-11-01 10:46 ` Joern Rennecke
2010-11-02 10:48 ` Paolo Bonzini
2010-11-02 16:43 ` David Daney [this message]
2010-11-01 17:46 ` Tom Tromey
2010-11-01 17:50 ` Andrew Haley
-- strict thread matches above, loose matches on Subject: below --
2010-10-31 19:09 Ian Lance Taylor
2010-11-01 8:59 ` Andrew Haley
2010-11-02 10:14 ` Laurent GUERBY
2010-11-02 15:32 ` Tom Tromey
2010-11-01 10:31 ` Dave Korn
2010-11-01 17:36 ` Ian Lance Taylor
2010-11-01 18:16 ` Diego Novillo
2010-11-01 18:58 ` Andrew Haley
2010-11-01 19:35 ` H.J. Lu
2010-11-02 3:39 ` Jeff Law
2010-11-02 3:58 ` H.J. Lu
2010-11-02 8:22 ` Eric Botcazou
2010-11-02 15:31 ` Tom Tromey
2010-11-02 16:25 ` Jeff Law
2010-11-02 5:12 ` Matthias Klose
2010-11-11 23:20 ` Ian Lance Taylor
2010-11-18 9:23 ` Mark Mitchell
2010-11-18 10:47 ` Andrew Haley
2010-11-18 13:42 ` H.J. Lu
2010-11-18 15:37 ` Mark Mitchell
2010-11-18 16:02 ` Diego Novillo
2010-11-18 15:23 ` Jeff Law
2010-11-18 17:19 ` Ian Lance Taylor
2010-11-18 17:58 ` Dave Korn
2010-11-18 20:53 ` Mark Wielaard
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=4CD03FAF.1070808@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=bonzini@gnu.org \
--cc=bosch@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=java@gcc.gnu.org \
--cc=joern.rennecke@embecosm.com \
--cc=stevenb.gcc@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).