Open drook opened 2 years ago
Seems like pipe2() call is missing on Solaris 11.x versions < 11.4. Sad.
CC @tklauser @golang/solaris
Looks like Solaris 11.4 came out in 2018. Would it be reasonable to make that a minimal requirement for Go support?
Would it be reasonable to make that a minimal requirement for Go support?
More generally: in order to detect regressions on a given port, the builder(s) for that port should be running the oldest OS version, and (ideally) also the newest OS version supported by the port. Since there is only one Solaris builder running (solaris-amd64-oraclerel
), the supported version range for Solaris is de facto exactly whatever version that builder happens to have installed. 😅
In triage: I think @bcmills is right; if we're not testing it I'm not sure we support that version. I was going to assign this to @golang/solaris but there doesn't appear to be anyone in there... @thanm notes that @rorth is the owner of the builder. Are you still actively maintaining the Solaris port?
CC @golang/illumos since this might be relevant to you as well.
We've had pipe2()
since 2013 so I believe we're good on the illumos front. Thanks for checking!
In triage: I think @bcmills is right; if we're not testing it I'm not sure we support that version. I was going to assign this to @golang/solaris but there doesn't appear to be anyone in there... @thanm notes that @rorth is the owner of the builder. Are you still actively maintaining the Solaris port?
While the solaris-amd64-oraclerel
builder does indeed run the latest Solaris 11.4 SRU/update, @ianlancetaylor regularly imports golang
into the GCC tree when a golang
release approaches, which still supports both Solaris 11.3 and 11.4, both being tested regularly. Thus I'd very much appreciate if support for targets without pipe2
could remain.
That said, I've never really maintained the Solaris port. I've inherited the builder from @binarycrusader long ago and keep it running, the primary intent being to keep golang
building and avoid unpleasant surprises once the next import into the GCC tree happens. Apart from that, I try to investigate specific issues if prompted or if I notice ongoing build failures.
If we don't have any maintainers for the Solaris port, that's not great. The port is not currently broken, but by the new port policy (#53383) if it gets into a broken state and nobody fixes it, it may end up getting removed.
Perhaps we should post on golang-dev looking for an owner. @rorth, @binarycrusader, @jclulow if you know anyone that might be interested please reach out to them if you have time.
For this particular issue, I think if we are supporting Solaris 11.3 indirectly through gccgo (and libruntime/libgo) then:
Marking as help wanted.
Env: Solaris: SunOS hyperion 5.11 11.3 i86pc i386 i86pc GCC:
Building toolchain:
Doesn't matter if I'm trying to built 32bit or 64 bit version of go binaries, the error stack is the same.