From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Compile pvops kernel xen/stable-2.6.32.x error Date: Wed, 27 Oct 2010 11:12:48 -0700 Message-ID: <4CC86BA0.5080506@goop.org> References: <4CC8605E.5080209@goop.org> <20101027175141.GA16318@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20101027175141.GA16318@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com, Teck Choon Giam List-Id: xen-devel@lists.xenproject.org On 10/27/2010 10:51 AM, Konrad Rzeszutek Wilk wrote: > On Thu, Oct 28, 2010 at 01:43:27AM +0800, Teck Choon Giam wrote: >>> Ah, how unpleasant. Unfortunately the problem isn't really with the >>> lines its pointing out, but with something earlier in the source (or >>> headers) which is also per-cpu, and gcc has decided there's a section >>> conflict between the two. Could you do "make arch/x86/mmu.i" and send >>> me the result? >> I guess you mean "make arch/x86/xen/mmu.i" instead? >> >> mock-chroot> make arch/x86/mmu.i >> make: *** No rule to make target `arch/x86/mmu.i'. Stop. >> mock-chroot> make arch/x86/xen/mmu. >> mmu.c mmu.h >> mock-chroot> make arch/x86/xen/mmu.i >> CHK include/linux/version.h >> CHK include/linux/utsrelease.h >> SYMLINK include/asm -> include/asm-x86 >> CALL scripts/checksyscalls.sh >> CPP arch/x86/xen/mmu.i >> mock-chroot> >> >> FYI, I am able to compile if I optimized the kernel configuration such >> as CPUSET, Power related such as battery, adaptors, laptop related >> etc. all disabled. The problem config is used from RHEL6 x86_64 >> kernel (ftp://ftp.redhat.com/pub/redhat/rhel/beta/6Server-beta2/x86_64/os/Packages/kernel-2.6.32-44.2.el6.x86_64.rpm) >> as base and just make oldconfig etc. to enable XEN related and there I >> got those errors :/ > This looks like your compiler is ancient. 4.1 is pretty old. Can you upgrade > it to a more modern version? It is old, but not ancient and still supported. And as Teck says, if its the disto standard compiler we definitely need to make sure it works. But the whole section mismatch thing is very annoying because its a behaviour which changes a lot from version to version, and is also very sensitive to config options and even small, semantically neutral code changes. J