On Mon, Oct 27, 2014 at 9:02 AM, Jan-Benedict Glaw wrote:
> On Mon, 2014-10-27 08:19:34 -0700, Ian Taylor wrote:
>> On Mon, Oct 27, 2014 at 8:06 AM, Jan-Benedict Glaw wrote:
>> > On Wed, 2014-10-22 20:36:53 -0700, Ian Taylor wrote:
>> > > This patch to the top level GCC configure script disable
On Mon, 2014-10-27 08:19:34 -0700, Ian Taylor wrote:
> On Mon, Oct 27, 2014 at 8:06 AM, Jan-Benedict Glaw wrote:
> > On Wed, 2014-10-22 20:36:53 -0700, Ian Taylor wrote:
> > > This patch to the top level GCC configure script disables the go
> > > languages on some systems where it is known to no
On Mon, Oct 27, 2014 at 8:06 AM, Jan-Benedict Glaw wrote:
>
> On Wed, 2014-10-22 20:36:53 -0700, Ian Taylor wrote:
>> This patch to the top level GCC configure script disables the go
>> languages on some systems where it is known to not work. Bootstrapped
>> on x86_64-unknown-gnu-linux.
>
> I do
Hi Ian,
On Wed, 2014-10-22 20:36:53 -0700, Ian Taylor wrote:
> This patch to the top level GCC configure script disables the go
> languages on some systems where it is known to not work. Bootstrapped
> on x86_64-unknown-gnu-linux.
I don't have a clue here, but in what way is Go broken for these
On Thu, Oct 23, 2014 at 8:39 AM, Pedro Alves 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-specif
On 10/22/14 21:36, Ian Taylor wrote:
This patch to the top level GCC configure script disables the go
languages on some systems where it is known to not work. Bootstrapped
on x86_64-unknown-gnu-linux.
OK for mainline?
Ian
2014-10-22 Ian Lance Taylor
* configure.ac: Disable the Go frontend
On 10/23/2014 04:31 PM, Ian Taylor wrote:
> On Thu, Oct 23, 2014 at 8:27 AM, Pedro Alves wrote:
>>
>> I think it'd be better if knowledge specific to subdirs was pushed down to
>> the subdirs, rather than being kept in the top level, in the direction
>> of how we disable libatomic, libsanitizer, e
On Thu, Oct 23, 2014 at 8:27 AM, Pedro Alves wrote:
>
> I think it'd be better if knowledge specific to subdirs was pushed down to
> the subdirs, rather than being kept in the top level, in the direction
> of how we disable libatomic, libsanitizer, etc. That is, by sourcing
> something in the sub
On 10/23/2014 04:36 AM, Ian Taylor wrote:
> This patch to the top level GCC configure script disables the go
> languages on some systems where it is known to not work. Bootstrapped
> on x86_64-unknown-gnu-linux.
>
> OK for mainline?
>
> Ian
>
> 2014-10-22 Ian Lance Taylor
>
> * configure.ac
