Evan Silberman <evan@jklol.net> wrote:
> I'm trying with this:
> 
> diff /usr/ports
> commit - 5fdc9dbcebbd57477b047430dfc2cc4e987537ef
> path + /usr/ports
> blob - a51e834910b7ee582f3be8d92a4e137a0cb46ad1
> file + devel/cabal/cabal.port.mk
> --- devel/cabal/cabal.port.mk
> +++ devel/cabal/cabal.port.mk
> @@ -85,7 +85,7 @@ MODCABAL_post-extract += \
>  MODCABAL_post-extract += \
>  	&& echo "package *\n ghc-options: -fdiagnostics-color=never" >> ${WRKSRC}/cabal.project.local \
>  	&& echo "package *\n ghc-options: -split-sections\n" >> ${WRKSRC}/cabal.project.local \
> -	&& echo "package ${MODCABAL_STEM}\n ld-options: -Wl,--gc-sections,--build-id" >> ${WRKSRC}/cabal.project.local
> +	&& echo "package ${MODCABAL_STEM}\n ld-options: -Wl,--gc-sections,--build-id,-z,nobtcfi" >> ${WRKSRC}/cabal.project.local
>  
>  # Automatically copies the cabal.project file if any.
>  MODCABAL_post-extract += \

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.

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.

Evan