Re: Linking userland with lld

2017-01-21 Thread Joerg Sonnenberger
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

Re: Linking userland with lld

2017-01-21 Thread Miod Vallat
> 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

Re: Linking userland with lld

2017-01-21 Thread Theo de Raadt
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

Linking userland with lld

2017-01-21 Thread Mark Kettenis
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