-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go,cmd/link: Adds shared linking support for FreeBSD/amd64 #29726
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
Conversation
This PR (HEAD: 7107014) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/go/+/157682 to see it. Tip: You can toggle comments from me using the |
Message from Gobot Gobot: Patch Set 1: Congratulations on opening your first change. Thank you for your contribution! Next steps: Most changes in the Go project go through a few rounds of revision. This can be During May-July and Nov-Jan the Go project is in a code freeze, during which Please don’t reply on this GitHub thread. Visit golang.org/cl/157682. |
Message from Brad Fitzpatrick: Patch Set 1: (1 comment) This is all that's required? Aren't there tests to enable too? Please don’t reply on this GitHub thread. Visit golang.org/cl/157682. |
Message from Ian Lance Taylor: Patch Set 1: You also need to change (*tester).supportedBuildMode in cmd/dist/test.go. Please don’t reply on this GitHub thread. Visit golang.org/cl/157682. |
Message from Kolby Crouch: Patch Set 1:
Ah sorry about that. I didn't even think to look for a test case. Should I just make a new pull request with this commit + the change in cmd/dist/test.go? Sorry for the noob mistakes. First time contributing to go, and first time dealing with Gerrit. Please don’t reply on this GitHub thread. Visit golang.org/cl/157682. |
Message from Ian Lance Taylor: Patch Set 1:
You should be able to add the change to cmd/dist/test.go to this change. You shouldn't need to create a new change. Though you can create a new change and close this one if that is easier. Please don’t reply on this GitHub thread. Visit golang.org/cl/157682. |
4a7ed1f
to
0f992b9
Compare
Message from Go Bot: Patch Set 1: Congratulations on opening your first change. Thank you for your contribution! Next steps: Most changes in the Go project go through a few rounds of revision. This can be During May-July and Nov-Jan the Go project is in a code freeze, during which Please don’t reply on this GitHub thread. Visit golang.org/cl/157682. |
Message from Kolby Crouch: Patch Set 1:
Ah sorry about that. I didn't even think to look for a test case. Should I just make a new pull request with this commit + the change in cmd/dist/test.go? Sorry for the noob mistakes. First time contributing to go, and first time dealing with Gerrit. Please don’t reply on this GitHub thread. Visit golang.org/cl/157682. |
Message from Ian Lance Taylor: Patch Set 1:
You should be able to add the change to cmd/dist/test.go to this change. You shouldn't need to create a new change. Though you can create a new change and close this one if that is easier. Please don’t reply on this GitHub thread. Visit golang.org/cl/157682. |
Fixes #29715