FreeBSD doesn't like rearranged program headers

[staticfloat]

FreeBSD has decided that the program header of ELF files must fit within the first page. This is a bit of a problem, as patchelf often relocates the program header to the end of the ELF header, causing it to no longer fit within the first page. I'm not sure the best way to fix this, but I thought I would open an issue so others that run into the program header too large issue that FreeBSD often spits out can gather here to discuss possible solutions (other than rewriting the FreeBSD dynamic loader, of course).

[ararslan]

I've submitted a companion bug report to FreeBSD: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229708

[domenkozar]

Could you try with 0.11 / master?

[ararslan]

Reproducing this 2 years later will be a bit tricky, as much has changed... The problematic binaries used originally are from the FreeBSD release asset from v1.0.1 of https://github.com/bicycle1885/XML2Builder. The infrastructure used to cross compile binaries has evolved, and the resulting libxml2 no longer exhibits this problem. @staticfloat, any idea on how we might be able to verify whether this has been fixed?

[vchuravy]

any idea on how we might be able to verify whether this has been fixed?

Apparently running patchelf on libLLVM.so also shows the problem.

[Mic92]

any idea on how we might be able to verify whether this has been fixed?

Apparently running patchelf on libLLVM.so also shows the problem.

Do you mean patching libLLVM.so with patchelf on freebsd?

[vchuravy]

Yeah:

 	patchelf --set-rpath '$ORIGIN:$ORIGIN/..' libLLVM.so

On the libLLVM from https://github.com/JuliaBinaryWrappers/libLLVM_jll.jl/releases/download/libLLVM-v13.0.0%2B0/libLLVM.v13.0.0.x86_64-unknown-freebsd.tar.gz

[ararslan]

FYI this has apparently been fixed upstream in FreeBSD and backported to multiple active release branches. See the bug report I opened a while back: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229708. Based on the timing, I imagine it will be in FreeBSD 12.3.

[ararslan]

Note though that the problem remains for current FreeBSD versions.