On Sat, Jan 21, 2017 at 10:58:59AM +0100, Mark Kettenis wrote:
> The problem here is that the code uses the SHA1 functions in
> libcrypto, but doesn't explicitly link against that library. With our
> ancient binutils we don't notice this, because we link against libtls,
> which as a DT_NEEDED entr
> The plan is to use lld (the llvm linker) on arm64 to avoid GLPv3
> binutils. Mostly works, but it triggers an issue in building ldapd
> and ldapctl.
>
> The problem here is that the code uses the SHA1 functions in
> libcrypto, but doesn't explicitly link against that library. With our
> ancien
I stole your diff yesterday, when I built a static snapshot for fun.
> The plan is to use lld (the llvm linker) on arm64 to avoid GLPv3
> binutils. Mostly works, but it triggers an issue in building ldapd
> and ldapctl.
>
> The problem here is that the code uses the SHA1 functions in
> libcrypto
The plan is to use lld (the llvm linker) on arm64 to avoid GLPv3
binutils. Mostly works, but it triggers an issue in building ldapd
and ldapctl.
The problem here is that the code uses the SHA1 functions in
libcrypto, but doesn't explicitly link against that library. With our
ancient binutils we