From: Ian Lance Taylor <iant@google.com>
To: Jeff Law <law@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, Uros Bizjak <ubizjak@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
GCJ-patches <java-patches@gcc.gnu.org>,
Andrew Haley <aph@redhat.com>
Subject: Re: [PATCH, libjava/classpath]: Fix overriding recipe for target 'gjdoc' build warning
Date: Wed, 12 Aug 2015 16:59:00 -0000 [thread overview]
Message-ID: <CAKOQZ8yjgJJn7KfFq-QM8Ua-n28LRzuY7r+AeYg8BRNnHqie7Q@mail.gmail.com> (raw)
In-Reply-To: <55CB7885.6090900@redhat.com>
On Wed, Aug 12, 2015 at 9:47 AM, Jeff Law <law@redhat.com> wrote:
>
> If you're comfortable with Go at this point and we have mechanisms in place
> to ensure Go only gets built on platforms that support Go, then I think we
> should go forward with replacing GCJ with Go.
We have the mechanism for disabling Go on systems where it will not
work. However, the list of such systems is undoubtedly incomplete at
this time.
In the top level configure.ac:
# Disable the go frontend on systems where it is known to not work. Please keep
# this in sync with contrib/config-list.mk.
case "${target}" in
*-*-darwin* | *-*-cygwin* | *-*-mingw* | *-*-aix*)
unsupported_languages="$unsupported_languages go"
;;
esac
# Disable libgo for some systems where it is known to not work.
# For testing, you can easily override this with --enable-libgo.
if test x$enable_libgo = x; then
case "${target}" in
*-*-darwin*)
# PR 46986
noconfigdirs="$noconfigdirs target-libgo"
;;
*-*-cygwin* | *-*-mingw*)
noconfigdirs="$noconfigdirs target-libgo"
;;
*-*-aix*)
noconfigdirs="$noconfigdirs target-libgo"
;;
esac
fi
next prev parent reply other threads:[~2015-08-12 16:59 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 [this message]
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
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=CAKOQZ8yjgJJn7KfFq-QM8Ua-n28LRzuY7r+AeYg8BRNnHqie7Q@mail.gmail.com \
--to=iant@google.com \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).