-
Notifications
You must be signed in to change notification settings - Fork 13
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
net: stop using go:linkname #895
Milestone
Comments
mmatczuk
added a commit
that referenced
this issue
Sep 4, 2024
Go 1.23 forbids go:linkname and thus prevents the build. Disable the check and continue business as usual. This commit shall be reverted when we can get rid of go:linkname. Relates to #895
Caused by #894 |
mmatczuk
added a commit
that referenced
this issue
Sep 4, 2024
Go 1.23 forbids go:linkname and thus prevents the build. Disable the check and continue business as usual. This commit shall be reverted when we can get rid of go:linkname. Relates to #895
mmatczuk
added a commit
that referenced
this issue
Sep 4, 2024
Go 1.23 forbids go:linkname and thus prevents the build. Disable the check and continue business as usual. This commit shall be reverted when we can get rid of go:linkname. Relates to #895
mmatczuk
added a commit
that referenced
this issue
Sep 4, 2024
Go 1.23 forbids go:linkname and thus prevents the build. Disable the check and continue business as usual. This commit shall be reverted when we can get rid of go:linkname. Relates to #895
|
This was referenced Sep 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Go 1.23 prevents us from accessing unexpected parts of standard library.
At the moment we use
config.go://go:linkname isDomainName net.isDomainName
utils/osdns/resolvconf.go://go:linkname resolvConf net.resolvConf
utils/osdns/resolvconf.go://go:linkname getSystemDNSConfig net.getSystemDNSConfig
resolver.go://go:linkname lookupStaticHost net.lookupStaticHost
We need to figure out what to do case by case.
The text was updated successfully, but these errors were encountered: