All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Dulloor <dulloor@gmail.com>
Subject: [PATCH] tools: fix libgcrypt detection
Date: Mon, 16 Nov 2009 09:35:35 +0100	[thread overview]
Message-ID: <4B010ED7.3070009@amd.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 614 bytes --]

Hi,

if we want to check the functionality of libgcrypt, we shouldn't test a 
function only exported by openssl, but instead the one actually used in 
the code.

Signed-off-by: Andre Przywara <andre.przywara@amd.com>

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448 3567 12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd; Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

[-- Attachment #2: check_gcrypt.patch --]
[-- Type: text/x-patch, Size: 385 bytes --]

diff -r bec27eb6f72c tools/blktap2/drivers/check_gcrypt
--- a/tools/blktap2/drivers/check_gcrypt	Sat Nov 14 10:32:59 2009 +0000
+++ b/tools/blktap2/drivers/check_gcrypt	Mon Nov 16 09:30:44 2009 +0100
@@ -4,8 +4,7 @@
 #include <gcrypt.h>
 int main(void) 
 {
-    char dummy[14];
-    MD5("DUMMY", 5, dummy);
+    gcry_md_hash_buffer(GCRY_MD_MD5, NULL, NULL, 0);
     return 0; 
 }
 EOF

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

                 reply	other threads:[~2009-11-16  8:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4B010ED7.3070009@amd.com \
    --to=andre.przywara@amd.com \
    --cc=dulloor@gmail.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.