Navigation Menu

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

net: could not determine kind of name for C.res_nclose on linux-amd64-alpine #56657

Closed
mknyszek opened this issue Nov 8, 2022 · 4 comments
Closed
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker Soon This needs to be done soon. (regressions, serious bugs, outages)
Milestone

Comments

@mknyszek
Copy link
Contributor

mknyszek commented Nov 8, 2022

Persistently failing since https://go.dev/cl/446179.

CC @rsc @ianlancetaylor

@mknyszek mknyszek added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker labels Nov 8, 2022
@mknyszek mknyszek added this to the Go1.20 milestone Nov 8, 2022
@mknyszek mknyszek added the Soon This needs to be done soon. (regressions, serious bugs, outages) label Nov 8, 2022
@mknyszek
Copy link
Contributor Author

mknyszek commented Nov 8, 2022

Actually, I'm not sure if linux-amd64-alpine is first class...

@mknyszek
Copy link
Contributor Author

mknyszek commented Nov 8, 2022

There appear to be similar, related errors on dragonfly and android but with a different symptom (-lresolv related).

@rsc
Copy link
Contributor

rsc commented Nov 8, 2022

#56660 for the -lresolv issue.

@gopherbot
Copy link

Change https://go.dev/cl/448797 mentions this issue: net: use res_search, not res_nsearch, on Linux

@golang golang locked and limited conversation to collaborators Nov 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. release-blocker Soon This needs to be done soon. (regressions, serious bugs, outages)
Projects
None yet
Development

No branches or pull requests

3 participants