From: Robert Love <rml@tech9.net>
To: "Udo A. Steinberg" <reality@delusion.de>
Cc: Dave Jones <davej@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
laughing@shared-source.org
Subject: Re: Linux 2.4.12-ac5
Date: 21 Oct 2001 21:26:58 -0400 [thread overview]
Message-ID: <1003714021.1014.144.camel@phantasy> (raw)
In-Reply-To: <3BD3743C.CF87EE89@delusion.de>
In-Reply-To: <Pine.LNX.4.30.0110220249230.17514-100000@Appserv.suse.de> <3BD3743C.CF87EE89@delusion.de>
On Sun, 2001-10-21 at 21:19, Udo A. Steinberg wrote:
> Dave Jones wrote:
> >
> > Odd, that part builds fine here. The missing declaration you get is
> > declared in fixmap.h, which is included from pgalloc.h. Untar a fresh tree,
> > and reapply the patch.
>
> Just in order to ensure I'm not insane, could you try building with the
> following .config file?
You aren't crazy, it doesn't build here either. The problem is that
fixmap.h only includes those defines if CONFIG_IO_APIC is defined.
Well, I don't have use IO_APIC (I am UP) but I do define
CONFIG_X86_APIC. So it does not compile.
So, the problem is that acpitable.c assumes you have both CONFIG_IO_APIC
and CONFIG_X86_APIC declared. It shouldn't. Even more important, why
is my system compiling acpitable.c now? I don't compile anything to do
with ACPI. What needs access to the ACPI tables via Mini-ACPI, now?
Robert Love
next prev parent reply other threads:[~2001-10-22 1:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 23:45 Linux 2.4.12-ac5 Alan Cox
2001-10-22 0:20 ` Udo A. Steinberg
2001-10-22 0:54 ` Dave Jones
2001-10-22 1:19 ` Udo A. Steinberg
2001-10-22 1:26 ` Robert Love [this message]
2001-10-22 8:05 ` Alan Cox
2001-10-22 8:03 ` Robert Love
2001-10-22 8:15 ` Alan Cox
2001-10-22 1:48 ` Dave Jones
2001-10-22 5:41 ` Dwayne C. Litzenberger
2001-10-22 7:56 ` Alan Cox
2001-10-22 8:05 ` Keith Owens
2001-10-23 6:57 ` Linux 2.4.12-ac5 typo Gregory Ade
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=1003714021.1014.144.camel@phantasy \
--to=rml@tech9.net \
--cc=davej@suse.de \
--cc=laughing@shared-source.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reality@delusion.de \
/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.