Summary: | dev-libs/libressl: cross-compile support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | popham |
Component: | Current packages | Assignee: | Cross compilation support <cross> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | blueness, jstein, libressl, popham, tsmksubc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Run elibtoolize to update ltmain.sh and trigger the regeneration of libtool |
Description
popham
2016-01-16 05:07:44 UTC
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. |