When I attempt to cross compile dev-libs/libressl, my build fails when relinking. The libressl sources include an ltmain.sh without the cross/link-ROOT patch of the libtool eclass. libtool therefore looks for libraries based at `/` instead of my sysroot. Reproducible: Always
Created attachment 423020 [details, diff] Run elibtoolize to update ltmain.sh and trigger the regeneration of libtool
I think that the libtool eclass is too automagic for security stuff. I'm thinking: * Localize a patch within libressl that does the libtool patching and trigger that patch with a `-vanilla` use flag, and * mark the package with a `+vanilla` IUSE flag? Or maybe: * Localize a patch within libressl that does the libtool patching and trigger that patch with a `libressl_libtoolize` use flag, and * mark the package with a `-libressl_libtoolize` IUSE flag?
This was fixed ages ago. All but the oldest ebuild calls elibtoolize. I successfully cross-compiled it for x86_64-w64-mingw32 a short while ago although that target may not have suffered from this issue.