Evan Silberman <evan@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

> Greg back to your question about when this worked, I wish I could tell
> you something meaningful. I think I had a pre-7.4 snap on this laptop
> vintage September, whenever I last updated the Pandoc port, and then I
> don't think I really turned it on between then and this week, when I
> upgraded. Good demonstration of the value of checking in with how things
> are working more often.

Yeah, if you can figure out when this started happening, it would be
helpful.

Thanks
Greg