From: Ian Taylor <iant@golang.org>
To: Pedro Alves <palves@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Patch RFA: Top-level configure patch: disable go on systems where it doesn't work
Date: Thu, 23 Oct 2014 18:27:00 -0000 [thread overview]
Message-ID: <CAOyqgcVFyfF9nVDXOf=QOZ09Jc_3DUq4MC+Z8rqFbWj-cZqfAg@mail.gmail.com> (raw)
In-Reply-To: <54492125.7090408@redhat.com>
On Thu, Oct 23, 2014 at 8:39 AM, Pedro Alves <palves@redhat.com> wrote:
> On 10/23/2014 04:31 PM, Ian Taylor wrote:
>>
>> My patch was, of course, just building on the existing
>> unsupported_languages support. You are suggesting that we move that
>> support from the top level configure script to the language-specific
>> config-lang.in scripts.
>
> AFAICS no target in the top level disables go yet, so we
> could IMO do the config-lang.in mechanism without moving any of
> the existing target checks for other languages. It'd be a small
> change that way.
That sounds like setting up yet another incomplete transition. I
would strongly prefer to have all languages act the same way.
Ian
next prev parent reply other threads:[~2014-10-23 18:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 6:30 Ian Taylor
2014-10-23 15:31 ` Pedro Alves
2014-10-23 15:35 ` Ian Taylor
2014-10-23 15:41 ` Pedro Alves
2014-10-23 18:27 ` Ian Taylor [this message]
2014-10-23 18:17 ` Jeff Law
2014-10-27 15:07 ` Jan-Benedict Glaw
2014-10-27 15:20 ` Ian Taylor
2014-10-27 16:03 ` Jan-Benedict Glaw
2014-10-27 16:57 ` Ian Taylor
2014-10-30 14:15 ` [PATCH] config-list.mk: Build Go only for supported targets (was: Patch RFA: Top-level configure patch: disable go on systems where it doesn't work) Jan-Benedict Glaw
2014-10-30 15:20 ` Ian Taylor
2014-10-30 19:43 ` Jan-Benedict Glaw
2014-10-31 0:44 ` Ian Taylor
2014-10-31 11:07 ` Jan-Benedict Glaw
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='CAOyqgcVFyfF9nVDXOf=QOZ09Jc_3DUq4MC+Z8rqFbWj-cZqfAg@mail.gmail.com' \
--to=iant@golang.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=palves@redhat.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).