From: "Natalie Protasevich" <protasnb@gmail.com>
To: linux-kernel@vger.kernel.org, rdreier@cisco.com
Cc: akpm@linux-foundation.org, vgoyal@in.ibm.com
Subject: Re: FW: CONFIG_X86_ES7000=y, CONFIG_X86_GENERICARCH=n, CONFIG_ACPI=y build broken
Date: Tue, 12 Jun 2007 14:49:01 -0700 [thread overview]
Message-ID: <32209efe0706121449j7a973d5w47c9ff0efe916bcd@mail.gmail.com> (raw)
In-Reply-To: <32209efe0706121432w705bfe51yb45f4fd08544267b@mail.gmail.com>
On 6/12/07, Natalie Protasevich <protasnb@gmail.com> wrote:
> >
> > From: Roland Dreier [mailto:rdreier@cisco.com]
> > Sent: Tuesday, June 12, 2007 1:14 PM
> > To: linux-kernel@vger.kernel.org; Protasevich, Natalie; Vivek Goyal
> > Cc: akpm@linux-foundation.org
> > Subject: CONFIG_X86_ES7000=y, CONFIG_X86_GENERICARCH=n, CONFIG_ACPI=y
> > build broken
> >
> > (sending to Vivek since he seems to be one of the last people to touch
> > this code)
> >
> > For some strange reason I found myself compiling a kernel with
> > CONFIG_X86_ES7000 and CONFIG_ACPI set and CONFIG_X86_GENERICARCH not
> > set. It died with
> >
> > arch/i386/kernel/built-in.o: In function `acpi_parse_madt':
> > boot.c:(.init.text+0x68b7): undefined reference to
> > `acpi_madt_oem_check'
> > arch/i386/kernel/built-in.o: In function `get_smp_config':
> > (.init.text+0x9f98): undefined reference to `mps_oem_check'
> > arch/i386/kernel/built-in.o: In function `connect_bsp_APIC':
> > (.init.text+0xa340): undefined reference to `enable_apic_mode'
> > arch/i386/kernel/built-in.o: In function `connect_bsp_APIC':
> > (.init.text+0xa370): undefined reference to `enable_apic_mode'
> >
> > this seems to be because eg acpi_madt_oem_check() and mps_oem_check()
> > are defined in arch/i386/mach-generic/es7000.c, but arch/i386/Makefile
> > only goes into mach-generic if CONFIG_X86_GENERICARCH is set.
> > I didn't track down why enable_apic_mode is broken yet.
> >
> > No patch because I don't understand how this subarch stuff is supposed
> > to build :(
> >
> > - R.
> >
>
> Roland,
> I can't reproduce the problem, with the git tree I just pulled. Can
> you please provide the config file?
Sorry, never mind - I just did...Will look at it also.
Thanks,
--Natalie
next prev parent reply other threads:[~2007-06-12 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19D0D50E9B1D0A40A9F0323DBFA04ACC023B0EB7@USRV-EXCH4.na.uis.unisys.com>
2007-06-12 21:32 ` Natalie Protasevich
2007-06-12 21:49 ` Natalie Protasevich [this message]
2007-06-12 21:53 ` Roland Dreier
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=32209efe0706121449j7a973d5w47c9ff0efe916bcd@mail.gmail.com \
--to=protasnb@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=vgoyal@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®