mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 04:45:48 +03:00
[GH-ISSUE #365] Build fails with "invalid reference to syscall.recvmsg" on Go 1.23 #206
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#206
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @svoop on GitHub (Oct 1, 2024).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/365
I'm trying to rebuild acme-dns on a Gentoo box after upping to Go 1.23 and it fails with:
Apparently, access to internal symbols has changed with Go 1.23, at least that's what's causing this error on other programs.
I'm not familiar with Go, so that's pretty much the end of the line for me. Any ideas how to rewrite the offending code not to use internal symbols?
@svoop commented on GitHub (Nov 25, 2024):
@joohoi The trend for now is to pin Go to 1.22 as a workaround. Since I don't know Go, could you drop a line as to how likely it is to make acme-dns compatible with newer versions of Go at all? From the frequency of commits, you might have bigger fish to fry which I'd totally understand!
In my particular case, I could switch to a ACME plugin which directly updates recs on my DNS provider, but I'd have to write an OS package (Gentoo ebuild that is) for this plugin first. I'm more inclined to stay with acme-dns, but if you intend to sunset acme-dns e.g. because of the workload to keep up with newer versions of Go, I'd start working on the package.
Thanks a bunch for a small update on where you intend to go with acme-dns. And big thanks for all the work you've already done... from one FOSS author to another! 👍
@svoop commented on GitHub (Dec 14, 2024):
@joohoi The missing compatibility with Go 1.23 starts to produce trouble with other software built with Go. Could you give a hint as to whether an update for Go 1.23 is realistic or not so folks like me can work around or move on? I'm a big fan of acme-dns, really like the way it solves the problems that come with DNS proof with Cerbot.
I see that you didn't commit much recently which is totally okay of course. But please drop a word here on whether you plan to abandon acme-dns... which would be sad but totally okay as well. Just, we have to know.
Thanks a bunch!!
@joohoi commented on GitHub (Dec 14, 2024):
Hi @svoop
I made the required changes and pushed a PR for Go 1.23 support #368
While it mentions the minimum required version of Go being 1.22, I tested it out with 1.23 as well. With the newest versions of all dependencies, 1.22 is the minimum required version though.
@thedix commented on GitHub (Dec 15, 2024):
@joohoi Thanks for your work!
Are there any plans to merge it to master?
@joohoi commented on GitHub (Dec 15, 2024):
Yeah, and to bump version to be sure. There seems to be an issue with the
linter, so I’ll have to fix that first though.
On Sun 15. Dec 2024 at 4.06, Dmitry Kononov @.***>
wrote:
@svoop commented on GitHub (Dec 15, 2024):
@joohoi Great, thanks so much!!
@hemna commented on GitHub (Aug 11, 2025):