From: Jeff Dike <jdike@addtoit•com>
To: Gabriel C <nix.or.die@googlemail•com>
Cc: linux-next@vger•kernel.org,
Linux Kernel list <linux-kernel@vger•kernel.org>,
user-mode-linux-devel@lists•sourceforge.net
Subject: Re: linux-next: UML build error
Date: Wed, 21 May 2008 16:05:15 -0400 [thread overview]
Message-ID: <20080521200515.GB12373@c2.user-mode-linux.org> (raw)
In-Reply-To: <48345B31.50904@googlemail.com>
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
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-05-21 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 17:26 linux-next: UML build error Gabriel C
2008-05-21 20:05 ` Jeff Dike [this message]
2008-05-21 20:20 ` Gabriel C
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=20080521200515.GB12373@c2.user-mode-linux.org \
--to=jdike@addtoit$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nix.or.die@googlemail$(echo .)com \
--cc=user-mode-linux-devel@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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