On Tue, May 26, 2015 at 9:17 AM, Lynn A. Boger
wrote:
>
> On 05/22/2015 05:50 PM, Ian Lance Taylor wrote:
>>
>> On Fri, May 22, 2015 at 3:11 PM, Andrew Chambers
>> wrote:
>>>
>>> I'm not suggesting breaking go conventions, I just think the default if
>>> no
>>> GOARCH is specified then it should
On 05/22/2015 05:50 PM, Ian Lance Taylor wrote:
On Fri, May 22, 2015 at 3:11 PM, Andrew Chambers
wrote:
I'm not suggesting breaking go conventions, I just think the default if no
GOARCH is specified then it should match --target.
Sounds good to me.
Perhaps we could check the symlink name f
On Fri, May 22, 2015 at 3:11 PM, Andrew Chambers
wrote:
>
> I'm not suggesting breaking go conventions, I just think the default if no
> GOARCH is specified then it should match --target.
Sounds good to me.
> Perhaps we could check the symlink name for the target triple if no GOARCH
> is set.
W
On Fri, May 22, 2015 at 2:01 PM, Andrew Chambers
wrote:
>>
>> For example, I've tested on an x86, built cross compilers for ppc64 and
>> ppc64le and then can invoke the native go tool (built to run on x86) to
>> compile with either target compiler by changing my GOARCH value. I don't
>> want to h
On Tue, Apr 14, 2015 at 6:14 AM, Lynn A. Boger
wrote:
> I got sidetracked with some bug fixes and decided the change for this was
> not real small.
>
> Should this be submitted to gofrontend, or to the golang master source?
Let's try it in the master repo. Thanks.
Ian
> On 03/17/2015 01:27 PM
I got sidetracked with some bug fixes and decided the change for this
was not real small.
Should this be submitted to gofrontend, or to the golang master source?
On 03/17/2015 01:27 PM, Ian Lance Taylor wrote:
On Tue, Mar 17, 2015 at 7:36 AM, wrote:
I have a patch to get gccgo to work on cr
On Tue, Mar 17, 2015 at 7:36 AM, wrote:
> I have a patch to get gccgo to work on cross.
>
> Is it too late to try and get this into gcc 5.0?
I think it's still possible. Depends on how small and safe it is.
Ian
> On Tuesday, February 3, 2015 at 2:18:39 PM UTC-6, Ian Lance Taylor wrote:
>>
>>
On Tue, Feb 3, 2015 at 11:52 AM, Lynn A. Boger
wrote:
>
> I've been experimenting with the go tools and how to make them work for
> cross gccgo builds.
>
> In golang I think there is just one 'go' tool and the cross build targets
> are specified by the setting of GOARCH and GOOS. So why couldn't
Hi,
I've been experimenting with the go tools and how to make them work for
cross gccgo builds.
In golang I think there is just one 'go' tool and the cross build
targets are specified by the setting of GOARCH and GOOS. So why
couldn't the same be done with gccgo?
That means, on any given
