WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Cannot compile Xen kernel

To: Mike Viau <viaum@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Cannot compile Xen kernel
From: Darko Petrović <darko.b.petrovic@xxxxxxxxx>
Date: Wed, 10 Feb 2010 17:26:30 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 10 Feb 2010 08:27:36 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=RS1PpUYxB4RM5K/uU+iry6x0lx5bmzsxjrJyg4cruas=; b=qNT3N3OA4rm9hq4Kco2iMPUdC1IBbZ8ChJ5SLL1PV2PZcXGzj0p/QkbNdfn+tfZMvf NDU4IGDn8KyIzFyBpOu+6uR2CjYLm/nROai/FbWvUVxOztB69YhMdhjNLMN6jrqdwZzG ILTxvFviu6aDgDlu/yHyKjQ43zvY+aKTkwhLM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=DqqjIFVY9e2I1p6NhDs1DWwOWsmjVW1WyaaMqqc9xBOcgIMdA5gJYLG5IxSXUufEfm dMrvH2x5am0C/wlCrAuUtXXhI/Y1r9D7eBGINUF4N7m28W7qU7ie2AjOGoLqcQzp4rGD xrfvVdIdM6amudy3wIYb0V4jScVMWVyrOebiQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BAY107-W33E3781A3B7B0265506892EF4F0@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <a46168061002100732h57942ed9qbf4c040df777c76a@xxxxxxxxxxxxxx> <BAY107-W33E3781A3B7B0265506892EF4F0@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Mike,

Thanks for your help! I am running a Q45 Express chipset, but your proposal solves the problem, now everything compiles fine.

However, there are some new issues but I will open a new topic.

Best regards,
Darko

2010/2/10 Mike Viau <viaum@xxxxxxxxxxxxxxx>
From: darko.b.petrovic@xxxxxxxxx
Date: Wed, 10 Feb 2010 16:32:41 +0100
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Cannot compile Xen kernel


Hello,

I have tried to compile the linux-2.6.18-xen kernel (the unstable version from the Mercurial repositories - http://xenbits.xensource.com/linux-2.6.18-xen.hg).
I use Debian Lenny and GCC 4.3.2.
However, the compilation stops with the following errors:

drivers/hwmon/coretemp.c:478: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__refdata’
drivers/hwmon/coretemp.c: In function ‘coretemp_init’:
drivers/hwmon/coretemp.c:523: error: ‘coretemp_cpu_notifier’ undeclared (first use in this function)
drivers/hwmon/coretemp.c:523: error: (Each undeclared identifier is reported only once
drivers/hwmon/coretemp.c:523: error: for each function it appears in.)
drivers/hwmon/coretemp.c: In function ‘coretemp_exit’:
drivers/hwmon/coretemp.c:545: error: ‘coretemp_cpu_notifier’ undeclared (first use in this function)
make[2]: *** [drivers/hwmon/coretemp.o] Error 1
make[1]: *** [drivers/hwmon] Error 2
make: *** [drivers] Error 2


Any suggestions? Is there any other xen-kernel known to work with unstable Xen 4.0.0?

--

I had that exact same error message at compile time with my Intel i7 860 & P55 chipset. Is your hardware similar?

I know the kernel can still be compiled if you remove the support for coretemp from your .config

lkddb platform "coretemp" :: CONFIG_HWMON CONFIG_SENSORS_CORETEMP :: drivers/hwmon/coretemp.c [0]

[0] -
http://cateee.net/lkddb/web-lkddb/HWMON.html

-M



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>