> Is there some way I can skip straight to building Go for my Solaris target using my existing Linux Go tools? Sorry, this question was foolish. Of course I can skip straight to building for Solaris, by using the make.bash script.
But as I pointed out earlier, > I looked at the POSIX docs <https://pubs.opengroup.org/onlinepubs/9699919799/idx/functions.html>, and POSIX only has a setregid() <https://pubs.opengroup.org/onlinepubs/9699919799/functions/setregid.html> function, and not a setresgid() <https://linux.die.net/man/2/setresgid> function. And > make.bash runs go build with the GOOS and GOARCH set to empty strings here <https://go.googlesource.com/go/+/refs/tags/go1.19/src/make.bash#201>. Please correct me if I am wrong, but my assumption is that if GOOS was properly set to solaris by make.bash, then linux_syscall.c would not be compiled, and then I would not get the compiler error I am seeing. On Saturday, August 27, 2022 at 2:40:52 PM UTC-4 Shane wrote: > I already have a working Go 1.19 for Linux with cgo support on my build > machine that I downloaded and installed from https://go.dev. Given this, > is it still necessary to build for the host? Is there some way I can skip > straight to building Go for my Solaris target using my existing Linux Go > tools? Or if I do that, does that break the guarantee of a consistent final > artifact? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/ab7f958c-e662-4f2e-a4ed-ef0426c174dcn%40googlegroups.com.
