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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 21 May 2008 22:20:39 +0200
From:	Gabriel C <nix.or.die@...glemail.com>
To:	Jeff Dike <jdike@...toit.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

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
--
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/