On Tue, Apr 24, 2018 at 10:15 AM, Philip Brown wrote:
>
> On Tuesday, April 24, 2018 at 6:56:21 AM UTC-7, Ian Lance Taylor wrote:
>>
>>
>> Sorry, you're quite right. I completely forgot that
>> -buildmode=archive is the default for a non-main package.
>>
>
> Okay, so just to close the loop on inf
On Tuesday, April 24, 2018 at 6:56:21 AM UTC-7, Ian Lance Taylor wrote:
>
>
> Sorry, you're quite right. I completely forgot that
> -buildmode=archive is the default for a non-main package.
>
>
Okay, so just to close the loop on information sharing, I think you are
saying that
-buildmode=arch
On Mon, Apr 23, 2018 at 10:32 PM, Philip Brown wrote:
> On Mon, Apr 23, 2018 at 9:23 PM, Ian Lance Taylor wrote:
>>
>>
>> There is no -buildmode=archive. Using -buildmode=c-archive should
>> work if that is what you want to do.
>>
>
> ORLLY? :-}
>
> $ go help buildmode
> The 'go build' and 'go i
On Mon, Apr 23, 2018 at 9:23 PM, Ian Lance Taylor wrote:
>
>
> There is no -buildmode=archive. Using -buildmode=c-archive should
> work if that is what you want to do.
>
ORLLY? :-}
$ go help buildmode
The 'go build' and 'go install' commands take a -buildmode argument which
indicates which kind
On Mon, Apr 23, 2018 at 6:40 PM, Philip Brown wrote:
>
> the docs at
> https://golang.org/doc/install/gccgo
> seem to mention how to use packages for your own code, but dont mention how
> to use third party packages.
>
> In other words, in situations where you would normally do
>
> go get github.o
the docs at
https://golang.org/doc/install/gccgo
seem to mention how to use packages for your own code, but dont mention how
to use third party packages.
In other words, in situations where you would normally do
go get github.org/blah/somepackage
What should you do for gccgo, once you have do
