From: Jos Hulzink <josh@stack.nl>
To: Robert Varga <nite@hq.alert.sk>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.45 build failed with ACPI turned on
Date: Fri, 1 Nov 2002 20:12:47 +0100 [thread overview]
Message-ID: <200211012012.47050.josh@stack.nl> (raw)
In-Reply-To: <20021031194547.GA3555@hq.alert.sk>
After some more puzzling, it becomes clear that much more ACPI code should rely on CONFIG_PM. (Sleep.c should not be compiled in at all without CONFIG_PM) As the ACPI guys seem awake, I assume this will be fixed soon. For now: don't forget to enable CONFIG_PM (Power Management in the root of ACPI / APM configuration)
Jos
On Thursday 31 October 2002 20:45, Robert Varga wrote:
> Hi
>
> Build fails with:
>
> drivers/acpi/sleep.c: In function `acpi_system_suspend':
> drivers/acpi/sleep.c:209: warning: implicit declaration of function
> `do_suspend_lowlevel' drivers/acpi/sleep.c: In function `acpi_sleep_init':
> drivers/acpi/sleep.c:707: `sysrq_acpi_poweroff_op' undeclared (first use in
> this function) drivers/acpi/sleep.c:707: (Each undeclared identifier is
> reported only once drivers/acpi/sleep.c:707: for each function it appears
> in.)
>
> The structure declaration is protected by
>
> #if defined(CONFIG_MAGIC_SYSRQ) && defined(CONFIG_PM)
>
> on line 640.
>
> Config file attached.
next prev parent reply other threads:[~2002-11-01 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 19:45 2.5.45 build failed with ACPI turned on Robert Varga
2002-11-01 19:02 ` Jos Hulzink
2002-11-01 19:12 ` Jos Hulzink [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-01 19:37 Grover, Andrew
2002-11-01 19:47 ` Dave Jones
2002-11-01 21:21 ` Jos Hulzink
2002-11-01 20:31 ` Dave Jones
2002-11-02 20:11 ` Jos Hulzink
2002-11-06 0:38 ` Bill Davidsen
2002-11-06 15:08 ` David Woodhouse
2002-11-06 16:33 ` Bill Davidsen
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=200211012012.47050.josh@stack.nl \
--to=josh@stack.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=nite@hq.alert.sk \
/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.