Believe me, it's not something I want to do. But, it's the only way that
building a Go program with dynamic linking will work.
Here's what I mean:
% go build -linkshared file1.go
internal/abi: go build internal/abi: copying
/home/jonf/.cache/go-build/06/0628acf114fffa5bc27f637027df97345926fcd84f
On Sat, Aug 12, 2023 at 10:27 AM jlfo...@berkeley.edu
wrote:
>
> Thanks.
>
> There's a more fundamental problem, though. Try running
>
> go build -linkshared hello.go
>
> as a non-privileged user. You'll get a bunch of permission denied messages.
> (I had mentioned this
> back in January). This i
Thanks.
There's a more fundamental problem, though. Try running
go build -linkshared hello.go
as a non-privileged user. You'll get a bunch of permission denied messages.
(I had mentioned this
back in January). This is why I'm fooling around running the compiler and
linker manually.
I suggest
On Fri, Aug 11, 2023 at 6:15 PM jlfo...@berkeley.edu
wrote:
>
> Now that Go 1.21 has been released, I've returned to trying to figure out how
> to
> dynamically link a Go program. Back in January I posted the results of my
> first attempt
> with an earlier version of Go, which was:
>
> 1) Buildi
Now that Go 1.21 has been released, I've returned to trying to figure out
how to
dynamically link a Go program. Back in January I posted the results of my
first attempt
with an earlier version of Go, which was:
1) Building a Go shared library by running
go install -buildmode=shared std
