Skip to content
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

syscall.MAFTER plan9 constant has disappeared #17921

Closed
sirnewton01 opened this issue Nov 15, 2016 · 6 comments
Closed

syscall.MAFTER plan9 constant has disappeared #17921

sirnewton01 opened this issue Nov 15, 2016 · 6 comments

Comments

@sirnewton01
Copy link
Contributor

sirnewton01 commented Nov 15, 2016

What version of Go are you using (go version)?

1.7.3

What operating system and processor architecture are you using (go env)?

plan9 386

What did you do?

I tried compiling an existing golang library that worked with earlier versions of go with the latest. It make a call to plan9 bind (syscall.Bind) and specifies that the bind should come after existing entries in that directory using the MAFTER flag.

The repository is here: https://bitbucket.org/mischief/draw9

What did you expect to see?

I expected that the code would continue to compile.

What did you see instead?

Instead, there is a compile error indicating that syscall.MAFTER is not defined in the syscall package.

@minux
Copy link
Member

minux commented Nov 15, 2016 via email

@bradfitz
Copy link
Contributor

plan9 is not a first class port and has never had the API checker enabled for it. (The API checker checks we never change or remove symbols between releases).

@bradfitz
Copy link
Contributor

@0intro, I'll let you prioritize how you want to fix this, if at all.

@0intro 0intro added this to the Go1.8Maybe milestone Nov 15, 2016
@0intro
Copy link
Member

0intro commented Nov 15, 2016

Thanks for reporting. I'll add these back for inclusion into Go 1.8.

@bradfitz
Copy link
Contributor

Related: #14892 tracks adding more GOOS/GOARCH pairs to the API checker.

@gopherbot
Copy link

CL https://golang.org/cl/33271 mentions this issue.

@golang golang locked and limited conversation to collaborators Nov 15, 2017
@rsc rsc unassigned 0intro Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants