Greg Steuck <gne...@openbsd.org> wrote: > Evan Silberman <e...@jklol.net> writes: > > > I should've figured out how to use readelf before I bothered with this, > > the NOBTCFI elf segment is already present in the ports in question. > > Above diff is irrelevant. It does seem significant that the ports that > > work fine (ghc and cabal-install) are, naturally, the ones that don't > > use cabal.port.mk to build. > > Right, these two programs are built differently. Yet, just like you, > I don't see any difference in the headers: > > % readelf -e $(which pandoc) | grep -A1 OPENBSD_NOBTCF > OPENBSD_NOBTCF 0x0000000000000000 0x0000000000000000 0x0000000000000000 > 0x0000000000000000 0x0000000000000000 E 0 > % readelf -e $(which cabal) | grep -A1 OPENBSD_NOBTCF > OPENBSD_NOBTCF 0x0000000000000000 0x0000000000000000 0x0000000000000000 > 0x0000000000000000 0x0000000000000000 E 0
Can you repeat for OPENBSD_WXNEED? On my syspatched 7.4-release VPS, pandoc from packages has wxneeded: ~$ uname -rsv OpenBSD 7.4 GENERIC#1336 ~$ readelf -Wl $(which pandoc) | grep OPENBSD_WXNEED OPENBSD_WXNEED 0x000000 0x0000000000000000 0x0000000000000000 0x000000 0x000000 E 0 Snapshot pandoc package on my laptop doesn't: ~ $ readelf -Wl $(which pandoc) | grep OPENBSD_WXNEED ~ $ Likewise doing a cabal build without ports infrastructure on my personal project produces a binary without OPENBSD_WXNEED. I would like to complete the loop and try building the same code on 7.4-release but my VPS /usr/local doesn't have enough space left to install ghc, lol. Evan
