Re: [go-nuts] How to control the symbol visibility of shared lib built from Go

2017-03-21 Thread Konstantin Khomoutov
On Mon, 20 Mar 2017 23:21:20 -0700 (PDT) Song Liu wrote: > Default symbol could break loading multiple shared lib implemented by > different version of go runtime, if there is one symbol with same > name but with different logic. This actually means they won't be compatible

Re: [go-nuts] How to control the symbol visibility of shared lib built from Go

2017-03-21 Thread Song Liu
Default symbol could break loading multiple shared lib implemented by different version of go runtime, if there is one symbol with same name but with different logic. And, the shared lib implemented by Go has too many symbols from the Go runtine and libraries, which will result in the loading

Re: [go-nuts] How to control the symbol visibility of shared lib built from Go

2017-03-20 Thread Ian Lance Taylor
On Mon, Mar 20, 2017 at 4:51 AM, Song Liu wrote: > > I am going to write a shared library using the Go, you know that the Go > runtime and used libraries are compiled into the library together. > > But it seems that all the symbols from this library is "DEFAULT", is there a >

[go-nuts] How to control the symbol visibility of shared lib built from Go

2017-03-20 Thread Song Liu
Hi, I am going to write a shared library using the Go, you know that the Go runtime and used libraries are compiled into the library together. But it seems that all the symbols from this library is "DEFAULT", is there a way to use the "HIDDEN" symbol visibility by default, but "DEFAULT" only