Re: [Xen-devel] Compiling 2.6.18-xen Dom0 Error: error: âcoretemp_cpu_notifierâ undeclared

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 23.05.13 at 04:47, Bei Guan <gbtju85@xxxxxxxxx> wrote:
> Can anyone help me to solve this problem that I have while compiling the
> 2.6.18.8 Dom0 kernel?
> My environment is Xen-4.2.2 + CentOS6.3 32bit + 2.6.18.8 Dom0. The details
> is as the following.
> 
> # make install-kernels
> ...
>   CC [M]  drivers/hwmon/coretemp.o
> /root/Xen/xen-4.2.2/linux-2.6.18-xen.hg/drivers/hwmon/coretemp.c: In
> function âcoretemp_initâ:
> /root/Xen/xen-4.2.2/linux-2.6.18-xen.hg/drivers/hwmon/coretemp.c:523:
> error: âcoretemp_cpu_notifierâ undeclared (first use in this function)
> /root/Xen/xen-4.2.2/linux-2.6.18-xen.hg/drivers/hwmon/coretemp.c:523:
> error: (Each undeclared identifier is reported only once
> /root/Xen/xen-4.2.2/linux-2.6.18-xen.hg/drivers/hwmon/coretemp.c:523:
> error: for each function it appears in.)
> /root/Xen/xen-4.2.2/linux-2.6.18-xen.hg/drivers/hwmon/coretemp.c: In
> function âcoretemp_exitâ:
> /root/Xen/xen-4.2.2/linux-2.6.18-xen.hg/drivers/hwmon/coretemp.c:545:
> error: âcoretemp_cpu_notifierâ undeclared (first use in this function)
> make[7]: *** [drivers/hwmon/coretemp.o] Error 1
> make[6]: *** [drivers/hwmon] Error 2
> make[6]: *** Waiting for unfinished jobs....
> ...
> 
> Any suggestion is appreciated.

For one, this sort of problem normally isn't that difficult to sort
out, so being on xen-devel we expect you to invest a little bit
of effort here yourself.

And then I'm not seeing similar build problems, and looking at the
code both producer and consumers of the symbol in question are
sitting in #ifdef CONFIG_HOTPLUG_CPU blocks, so I can't really
see how (without you having modified the code) the consumers
would get compiled without the producer also getting compiled.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel