Repository navigation
Lifting the gotosocial amd64 restriction #143
Description
Activity
I've followed that discussion, but didn't see that there's a go build-tag for that now.
Usually "not released", "up for testing" and similar states unless they fix a grave issue etc mean that this is a no-go for pkgsrc by default.
There should be no build difference, so I'm leaning towards just committing this, given the (probably) smaller userbase of pkgsrc gotosocial users@daenney is the restriction limited to 64bits still, or what's the limitation now?
The tag is now turned on as an option by default in the pkgsrc package, can be turned off in custom builds.
It should be fine on 32-bit and 64-bit platforms currently. The wazero WASM runtime should be fine, and afaik there shouldn't be any issues with the SQLite driver either. So I would expect netbsd/386, netbsd/amd64, netbsd/arm and netbsd/arm64 to work.
However, I don't think anyone's tested 32-bit GtS on anything other than Linux. It's the only platform we ship 32-bits builds for as well, and only on ARM.
- added a commit that references this issue
on Jun 18, 2024 - added a commit that references this issue
on Sep 19, 2024 - added a commit that references this issue
on Oct 21, 2024 - added 2 commits that reference this issue
on Dec 2, 2024 - added a commit that references this issue
on Dec 11, 2024 - added a commit that references this issue
on Jan 28, 2025 - added a commit that references this issue
on Jan 30, 2025 79 remaining items
- added 3 commits that reference this issue
on Jul 30, 2026 - added 2 commits that reference this issue
on Aug 25, 2026
Since GtS 0.16.0 there is a way to build with a SQLite driver that we access through WASM, which would lift the amd64 restriction currently in place as a consequence of using the modernc transpiled driver:
pkgsrc/www/gotosocial/Makefile
Lines 69 to 78 in eaf7753
There was initially an issue with that driver on the BSD family but that was resolved in the driver before we cut this release. It's safe to use and expected to perform just fine.
We're currently keeping it behind a go build tag,
wasmsqlite3, and we do consider it slightly experimental. However, the plan is to switch to this Soon™ and a number of people including two of the maintainers run this build on their own instances without any issues.I'm not familiar enough with how pkgsrc works, but if there's some kind of way to give people the option to try it out if they want to run on aarch64, this could be a way of achieving that already before the next release.
Getting any feedback on whether this build works out well for folks running it on NetBSD would also be very helpful.
// cc @nikkicoon