From: "Olivier B." <xen.list@daevel.fr>
To: xen-devel@lists.xensource.com
Subject: Re: Errors while compiling stable-2.6.32.x
Date: Fri, 28 May 2010 09:50:52 +0200 [thread overview]
Message-ID: <4BFF75DC.8030302@daevel.fr> (raw)
In-Reply-To: <4BFF44B5.6040402@goop.org>
Le 28/05/2010 06:21, Jeremy Fitzhardinge a écrit :
> On 05/27/2010 03:41 PM, Olivier B. wrote:
>
>> Hi,
>>
>> I'm trying to compile dom0 pv_ops kernel, the s table-2.6.32.x branch.
>>
>> I first obtained that error :
>>
>> drivers/acpi/processor_core.c:411: error: static declaration of
>> ‘acpi_processor_add_fs’ follows non-static declaration
>> include/acpi/processor.h:242: note: previous declaration of
>> ‘acpi_processor_add_fs’ was here
>> drivers/acpi/processor_core.c:415: error: static declaration of
>> ‘acpi_processor_remove_fs’ follows non-static declaration
>> include/acpi/processor.h:243: note: previous declaration of
>> ‘acpi_processor_remove_fs’ was here
>> make[3]: *** [drivers/acpi/processor_core.o] Erreur 1
>> make[2]: *** [drivers/acpi] Erreur 2
>> make[1]: *** [drivers] Erreur 2
>>
>>
>>
>> So I disabled ACPI, then I obtain this error :
>>
> You need ACPI in dom0; I think there should probably be a dependency on
> it if there isn't already. This problem can be resolved by enabling
> CONFIG_ACPI_PROCFS.
>
> J
>
>
You're right, it was just a .config problem, thanks !
But CONFIG_ACPI_PROCFS is marked as "deprecated", it is strange than xen
pv_ops - which is recent - depends of it, no ?
Thanks again,
Olivier
next prev parent reply other threads:[~2010-05-28 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 22:41 Errors while compiling stable-2.6.32.x Olivier B.
2010-05-27 23:15 ` Aravindh Puthiyaparambil
2010-05-27 23:24 ` Olivier B.
2010-05-28 4:21 ` Jeremy Fitzhardinge
2010-05-28 7:50 ` Olivier B. [this message]
2010-05-28 19:11 ` Jeremy Fitzhardinge
2010-05-28 8:52 ` Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BFF75DC.8030302@daevel.fr \
--to=xen.list@daevel.fr \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users-bounces@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.