Re: [go-nuts] Re: buildmode=c-archive and statically linking into another lib

thank you~I got it. 在 2019年8月28日星期三 UTC+8上午11:59:42，Justin Israel写道： > > > > On Wed, Aug 28, 2019, 3:47 PM > wrote: > >> I find the package you build with 'go build >> buildmode=c-archive/c-shared', when you build you code with the lib, the >> outer need to have main func, I don't know why. >>

Re: [go-nuts] Re: buildmode=c-archive and statically linking into another lib

On Wed, Aug 28, 2019, 3:47 PM wrote: > I find the package you build with 'go build buildmode=c-archive/c-shared', > when you build you code with the lib, the outer need to have main func, I > don't know why. > That requirement is documented here: https://golang.org/cmd/go/#hdr-Build_modes > 在

[go-nuts] Re: buildmode=c-archive and statically linking into another lib

I find the package you build with 'go build buildmode=c-archive/c-shared', when you build you code with the lib, the outer need to have main func, I don't know why. 在 2016年5月18日星期三 UTC+8上午11:11:57，Justin Israel写道： > > I'm wondering if someone can tell me if this is either a limitation of >

[go-nuts] Re: buildmode=c-archive and statically linking into another lib

On Friday, April 12, 2019 at 1:21:25 PM UTC+12, Chao Chen wrote: > Do you any progress to solve the problem? I meet the same problem. > > > when I call golang build shared library on python from alpine 3.9 > container.failed with OSError: Error relocating ./cc.so: : initial-exec TLS > resolves

[go-nuts] Re: buildmode=c-archive and statically linking into another lib

*Do you any progress to solve the problem? I meet the same problem.* w hen I call golang build shared library on python from alpine 3.9 container.failed with OSError: