On 2025/02/19 03:53, Kurt Mosiejczuk wrote: > On Tue, Feb 18, 2025 at 09:41:05PM -0600, Maximo Pech wrote: > > Hi @ports > > > I've noticed that official binaries for OpenBSD are available from > > upstream as you can see here > > https://docs.ipfs.tech/install/command-line/#install-official-binary-distributions. > > Also those are a newer version than the one we have in ports and they > > offer ipfs-cluster OpenBSD binaries as well, which we don't have in > > ports. > > Which version of OpenBSD did they build against? Did you test them?
Looking at the amd64 binary, it is probably new enough to run: $ readelf -l ipfs | grep NOBT OPENBSD_NOBTCF 0x0000000000000000 0x0000000000000000 0x0000000000000000 > Did they just assume that since it is go, they could cross-compile? they probably did cross-compile: $ objdump -p ipfs|grep NEEDED NEEDED libc.so NEEDED libpthread.so (the packaged version of the go compiler on OpenBSD uses the exact versions of those libraries; crosscompiling just the base name). > OpenBSD doesn't maintain ABI compatibility from one release to the > next. right. there is no guarantee that currently working binaries will stay working, or that upstream will provide new binaries when needed after a change in OpenBSD (especially for a change in snapshots that hasn't made it into a release yet). > We make sure the packages built from the ports tree stay > working. well, sometimes. there are go things still broken which probably broke when direct syscall was prohibited.
