Re: [gofrontend-dev] Re: GO tools for gccgo cross

2015-05-26 Thread Ian Lance Taylor
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

Re: [gofrontend-dev] Re: GO tools for gccgo cross

2015-05-26 Thread Lynn A. Boger
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

Re: [gofrontend-dev] Re: GO tools for gccgo cross

2015-05-22 Thread Ian Lance Taylor
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

Re: [gofrontend-dev] Re: GO tools for gccgo cross

2015-05-22 Thread Ian Lance Taylor
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