-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
os/user: fails to compile with 'osusergo' tag on linux/amd64 #24841
Comments
Change https://golang.org/cl/106837 mentions this issue: |
@sbinet thanks for the catch (and the fix) 🤝 |
Change https://golang.org/cl/107299 mentions this issue: |
Change https://golang.org/cl/107300 mentions this issue: |
Fixes #24841 Updates #24845 Change-Id: Ia7e2deefe64c12ee8a76ce6ed9f9e003e912b161 Reviewed-on: https://go-review.googlesource.com/107299 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
… windows Would've caught two regressions so far, and found two more. Updates #24841 Updates #24845 (package net remains) Change-Id: I57ad06eb54e04b8c99b5d2e7f24c77ad865224e8 Reviewed-on: https://go-review.googlesource.com/107300 Reviewed-by: Ian Lance Taylor <iant@golang.org>
Change https://golang.org/cl/107304 mentions this issue: |
Verified that on on Linux, with: CGO_ENABLED=1 GOOS=solaris go install --tags=osusergo ... it builds now. Updates #24841 Updates #24845 Change-Id: I49f40532bc2a13a9d282771592fc8d7f116b1902 Reviewed-on: https://go-review.googlesource.com/107304 Reviewed-by: Mikio Hara <mikioh.mikioh@gmail.com>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
no.
osusergo
is for next release.What operating system and processor architecture are you using (
go env
)?What did you do?
What did you expect to see?
A completely static, no-libc,
os/user
package being successfully built.What did you see instead?
couldn't see anything through my tears. but I have a CL coming up.
The text was updated successfully, but these errors were encountered: