From: NightStrike <nightstrike@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
gcc@gcc.gnu.org, java@gcc.gnu.org, hp@axis.com, hp@bitrange.com
Subject: Re: Target library disabling at toplevel
Date: Wed, 23 Mar 2011 11:49:00 -0000 [thread overview]
Message-ID: <AANLkTin-j0YR9R0AdNEr8YLroDH8CU6D4oPa=gnr_6j3@mail.gmail.com> (raw)
In-Reply-To: <mcrlj06reqg.fsf@google.com>
On Tue, Mar 22, 2011 at 6:07 PM, Ian Lance Taylor <iant@google.com> wrote:
> "Joseph S. Myers" <joseph@codesourcery.com> writes:
>
>> Why do a great many targets disable libgcj by default in the toplevel
>> configure.ac?
>
> I believe that it's just a hack: libgcj doesn't build on the target, but
> gcc/java does. Disabling libgcj lets the gcc configure/make complete in
> a natural way.
>
> unsupported_languages is a clearly superior approach, but it postdates
> many of the cases in which libgcj is added to noconfigdirs.
In some cases, like for x86_64-w64-mingw (Win64), we can build gcj
fine, and we intend to support a java compiler. However, at present,
we cannot build libgcj because the boehm-gc in the tree is several
years out of date. Once Hans, or someone else with enough skill,
updates that, we can turn on libgcj. Until then, we'd like to make
sure that building the compiler doesn't break.
Given how out of date certain dependencies are for libgcj, I would not
be surprised if other targets suffered the same fate.
next prev parent reply other threads:[~2011-03-23 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 19:51 Joseph S. Myers
2011-03-22 21:50 ` Hans-Peter Nilsson
2011-03-22 22:07 ` Joseph S. Myers
2011-03-22 22:07 ` Ian Lance Taylor
2011-03-23 11:49 ` NightStrike [this message]
2011-03-23 11:24 ` Richard Sandiford
2011-03-23 16:51 ` Paolo Bonzini
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='AANLkTin-j0YR9R0AdNEr8YLroDH8CU6D4oPa=gnr_6j3@mail.gmail.com' \
--to=nightstrike@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hp@axis.com \
--cc=hp@bitrange.com \
--cc=iant@google.com \
--cc=java@gcc.gnu.org \
--cc=joseph@codesourcery.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).