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
| ||
|
Date: Thu, 22 Jul 2010 23:05:10 -0700 From: Jeremy Fitzhardinge <jeremy@...p.org> To: Stephen Rothwell <sfr@...b.auug.org.au> CC: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: linux-next: build failure after merge of the xen tree On 07/22/2010 09:01 PM, Stephen Rothwell wrote: > arch/x86/xen/enlighten.c:71: error: __pcpu_scope_xen_vcpu causes a section type conflict > arch/x86/xen/enlighten.c:72: error: __pcpu_scope_xen_vcpu_info causes a section type conflict > arch/x86/xen/enlighten.c:71: error: __pcpu_unique_xen_vcpu causes a section type conflict > arch/x86/xen/enlighten.c:72: error: __pcpu_unique_xen_vcpu_info causes a section type conflict > arch/x86/xen/enlighten.c:558: error: __pcpu_unique_idt_desc causes a section type conflict > arch/x86/xen/enlighten.c:760: error: __pcpu_unique_xen_cr0_value causes a section type conflict > > Not sure what has caused this. I have dropped the xen tree for today. > > gcc version 4.4.4 binutils version 2.20.1. > I've updated upstream/xen with the patch I just posted to fix this problem. Thanks, J -- 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/
Powered by blists - more mailing lists