From: Gabriel C <nix.or.die@googlemail.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: linux-next: UML build error
Date: Wed, 21 May 2008 22:20:39 +0200 [thread overview]
Message-ID: <48348417.9090103@googlemail.com> (raw)
In-Reply-To: <20080521200515.GB12373@c2.user-mode-linux.org>
Jeff Dike wrote:
> 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.
Yes is fixes this error , however I get now another one but this one seems to be an compiler bug.
...
CC arch/um/sys-x86_64/um_module.o
LD arch/um/sys-x86_64/subarch.o
LD arch/um/sys-x86_64/built-in.o
LD arch/x86/crypto/built-in.o
CC kernel/sched.o
In file included from kernel/sched.c:1842:
kernel/sched_idletask.c: In function 'check_preempt_curr_idle':
kernel/sched_idletask.c:20: internal compiler error: in cgraph_estimate_size_after_inlining, at ipa-inline.c:188
...
This is gcc 4.3.0 ( with backports of some known fixed bugs ).
I try to build latest snapshot of gcc 4.3* later on today and try with this one.
>
> Jeff
>
Gabriel
prev parent reply other threads:[~2008-05-21 20:20 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
2008-05-21 20:20 ` Gabriel C [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=48348417.9090103@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).