[openssh-commits] [openssh] 01/02: Fix sha2 MAKE_CLONE no-op definition
    git+noreply at mindrot.org 
    git+noreply at mindrot.org
       
    Thu Feb  6 12:17:14 AEDT 2020
    
    
  
This is an automated email from the git hooks/post-receive script.
djm pushed a commit to branch master
in repository openssh.
commit 9716e8c4956acdd7b223d1642bfa376e07e7503d
Author: Michael Forney <mforney at mforney.org>
Date:   Wed Nov 27 19:17:26 2019 -0800
    Fix sha2 MAKE_CLONE no-op definition
    
    The point of the dummy declaration is so that MAKE_CLONE(...) can have
    a trailing semicolon without introducing an empty declaration. So,
    the macro replacement text should *not* have a trailing semicolon,
    just like DEF_WEAK.
---
 openbsd-compat/sha2.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/openbsd-compat/sha2.c b/openbsd-compat/sha2.c
index e63324c9..e36cc24e 100644
--- a/openbsd-compat/sha2.c
+++ b/openbsd-compat/sha2.c
@@ -42,7 +42,7 @@
     !defined(HAVE_SHA512UPDATE)
 
 /* no-op out, similar to DEF_WEAK but only needed here */
-#define MAKE_CLONE(x, y)	void __ssh_compat_make_clone_##x_##y(void);
+#define MAKE_CLONE(x, y)	void __ssh_compat_make_clone_##x_##y(void)
 
 #include <string.h>
 #include <sha2.h>
-- 
To stop receiving notification emails like this one, please contact
djm at mindrot.org.
    
    
More information about the openssh-commits
mailing list