linux-kernel - Re: linux-next: UML build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080521200515.GB12373@c2.user-mode-linux.org>
Date:	Wed, 21 May 2008 16:05:15 -0400
From:	Jeff Dike <jdike@...toit.com>
To:	Gabriel C <nix.or.die@...glemail.com>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-next@...r.kernel.org,
	user-mode-linux-devel@...ts.sourceforge.net
Subject: Re: linux-next: UML build error

On Wed, May 21, 2008 at 07:26:09PM +0200, Gabriel C wrote:
>   CC      arch/um/sys-x86_64/ksyms.o
> arch/um/sys-x86_64/ksyms.c:5: error: '__memcpy' undeclared here (not in a function)
> arch/um/sys-x86_64/ksyms.c:5: warning: type defaults to 'int' in declaration of '__memcpy'

Does the patch below help?  There's gcc-version-dependent logic in
include/asm-x86/string_64.h which decides whether to declare memcpy or
__memcpy and it looks like you're hitting that.

	     	      Jeff

-- 
Work email - jdike at linux dot intel dot com

Index: linux-2.6.22/arch/um/sys-x86_64/ksyms.c
===================================================================
--- linux-2.6.22.orig/arch/um/sys-x86_64/ksyms.c	2008-04-23 13:07:23.000000000 -0400
+++ linux-2.6.22/arch/um/sys-x86_64/ksyms.c	2008-05-21 16:03:03.000000000 -0400
@@ -2,4 +2,8 @@
 #include "asm/string.h"
 
 /*XXX: we need them because they would be exported by x86_64 */
+#if (__GNUC__ == 4 && __GNUC_MINOR__ >= 3) || __GNUC__ > 4
+EXPORT_SYMBOL(memcpy);
+#else
 EXPORT_SYMBOL(__memcpy);
+#endif
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/