From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pvops dom0 compile issues Date: Fri, 04 Dec 2009 11:26:00 -0800 Message-ID: <4B196248.4030708@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Michael D Labriola Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 12/04/09 04:49, Michael D Labriola wrote: > Jeremy, > > I've been playing with your pvops tree for a few weeks pretty > successfully. > My first attempt had some strange linking errors that I wrote off as a > misconfiguration on my part. I just pulled fresh from your xen/master > branch and snagged the example 32bit .config from the pvops Wiki and tried > to do a fresh compile. > > The first problem I had was some inlining errors in mptsas.c. I'm > assuming > that since that driver is enabled in the example .config that it compiles > for you... which means it's related to compiler differences perhaps? > Anyway, I attached a patch that fixed this. Basically just moved the > offending function to before it's first invocation. > > Now that that compile error is fixed, I get all the way to linking and get > this: > > drivers/built-in.o: In function `kmalloc': > include/trace/events/kmem.h:47: undefined reference to `.L1445' > > I also saw some warnings suggesting I do a 'make > CONFIG_DEBUG_SECTION_MISMATCH=y', so I've done that and attached the last > page or so of output as well. > > I got these errors to go away last time I compiled by gutting ALL the > debug stuff out of my .config... but I don't want to do that. > > Any ideas? I'm trying to get up to speed on this stuff, but am definitely > feeling a bit over my head. ;-) > > -Mike > > PS - I'm using gcc 3.4.6 on a custom linux distro forked off of fc5 a long > time ago... > gcc 3.4.6 is known to have compilation problems with pvops kernels, apparently because of 42854dc0a6320. Bug http://bugzilla.kernel.org/show_bug.cgi?id=14729 is tracking it, but its not clear what the right fix is. It's interesting you're seeing a different failure mode. I was wondering if anyone is still using 3.4.6, but I guess you've answered that question. Nevertheless, I'd recommend upgrading if you can. J