On Mon, Jun 06, 2016 at 06:05:35PM -0400, Mike Frysinger wrote:
> From: Mike Frysinger
>
> OpenSSL's libcrypto always defines AES symbols with the same names as
> qemu's local aes code. This is problematic when enabling at least curl
> as that frequently also uses libcrypto. It might not be not
From: Mike Frysinger
OpenSSL's libcrypto always defines AES symbols with the same names as
qemu's local aes code. This is problematic when enabling at least curl
as that frequently also uses libcrypto. It might not be noticed when
running, but if you try to statically link, everything falls dow
