From: Christian Brunner <chb@muc.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] rbd: don't link with -lcrypto
Date: Sun, 13 Mar 2011 22:16:21 +0100 [thread overview]
Message-ID: <AANLkTim5J0pyXSj0T6-A8ryL_+gFd87mdTj+6SDAYzex@mail.gmail.com> (raw)
In-Reply-To: <1299478669-11231-1-git-send-email-aurelien@aurel32.net>
You are right, libcrypto can be omitted.
(Recent versions of ceph use crypto++ anyway.)
Thanks, Christian
Reviewed-by: Christian Brunner <chb@muc.de>
2011/3/7 Aurelien Jarno <aurelien@aurel32.net>:
> rbd support tries to both link with -lrados and -lcrypto. While the
> first one is of course necessary, the second is not necessary (only
> librados ifself needs to link with libcrypto).
>
> This fixes a licensing issue: qemu as a whole is GPL v2, and thus can't
> be linked with OpenSSL without an exception in the license, which seems
> difficult to get given the number of persons involved.
>
> Cc: Christian Brunner <chb@muc.de>
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
> ---
> configure | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/configure b/configure
> index ef51a58..5932e39 100755
> --- a/configure
> +++ b/configure
> @@ -1801,7 +1801,7 @@ if test "$rbd" != "no" ; then
> #include <rados/librados.h>
> int main(void) { rados_initialize(0, NULL); return 0; }
> EOF
> - rbd_libs="-lrados -lcrypto"
> + rbd_libs="-lrados"
> if compile_prog "" "$rbd_libs" ; then
> librados_too_old=no
> cat > $TMPC <<EOF
> --
> 1.7.2.3
>
>
>
prev parent reply other threads:[~2011-03-13 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 6:17 [Qemu-devel] [PATCH] rbd: don't link with -lcrypto Aurelien Jarno
2011-03-13 21:16 ` Christian Brunner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTim5J0pyXSj0T6-A8ryL_+gFd87mdTj+6SDAYzex@mail.gmail.com \
--to=chb@muc.de \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).