From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.22-rc3-g184b812f build #294 failed in: undefined reference to `enable_apic_mode'
Date: Sat, 2 Jun 2007 16:40:52 -0700 [thread overview]
Message-ID: <20070602164052.6a36377f.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200706012319.23761.toralf.foerster@gmx.de>
On Fri, 1 Jun 2007 23:19:17 +0200 Toralf Förster wrote:
> Hello,
>
> the build with the attached .config failed, make ends with:
> ...
> UPD include/linux/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> arch/i386/kernel/built-in.o: In function `get_smp_config':
> : undefined reference to `mps_oem_check'
> arch/i386/kernel/built-in.o: In function `connect_bsp_APIC':
> : undefined reference to `enable_apic_mode'
> make: *** [.tmp_vmlinux1] Error 1
>
> This .config was made in this way :
> make mrproper && make rndconfig && <tweak it to ThinkPad T41> && make oldconfig && make
This sort-of-randconfig is still for Unisys ES7000 sub-architecture,
so tweaking it to Thinkpad T41 doesn't get you much of anything that
is useful. I think you can drop that step.
If you tweak it like this:
115c115
< # CONFIG_X86_PC is not set
---
> CONFIG_X86_PC=y
123c123
< CONFIG_X86_ES7000=y
---
> # CONFIG_X86_ES7000 is not set
and run 'make oldconfig', it will build.
I don't find this particular randconfig (#294) interesting, but
sometimes they can be, so don't stop trying them, please.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-06-02 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 21:19 Toralf Förster
2007-06-02 23:40 ` Randy Dunlap [this message]
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=20070602164052.6a36377f.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=toralf.foerster@gmx.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 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®