From: Andi Kleen <ak@suse.de>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-git latest build broken on UP x86-64
Date: Wed, 23 Nov 2005 04:11:04 +0100 [thread overview]
Message-ID: <20051123031104.GC20775@brahms.suse.de> (raw)
In-Reply-To: <20051122190202.40efabfb@localhost.localdomain>
On Tue, Nov 22, 2005 at 07:02:02PM -0800, Stephen Hemminger wrote:
> This looks new, it happens on Fedora Core 4 with UP x86-64.
>
> arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/main.c:225: error: ???ipi_handler??? undeclared (first use in this function)
> arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/main.c:225: error: (Each undeclared identifier is reported only once
> arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/main.c:225: error: for each function it appears in.)
> make[2]: *** [arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/main.o] Error 1
> make[2]: Target `__build' not remade because of errors.
> make[1]: *** [arch/x86_64/kernel/../../i386/kernel/cpu/mtrr] Error 2
>
> arch/x86_64/kernel/nmi.c:155: error: ???nmi_cpu_busy??? undeclared (first use in this function)
> arch/x86_64/kernel/nmi.c:155: error: (Each undeclared identifier is reported only once
> arch/x86_64/kernel/nmi.c:155: error: for each function it appears in.)
> make[1]: *** [arch/x86_64/kernel/nmi.o] Error 1
> make[1]: Target `__build' not remade because of errors.
> make: *** [arch/x86_64/kernel] Error 2
Works for me with -git2 and defconfig changed to UP. config please and last changeset.
-Andi
next prev parent reply other threads:[~2005-11-23 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 3:02 2.6.15-git latest build broken on UP x86-64 Stephen Hemminger
2005-11-23 3:11 ` Andi Kleen [this message]
2005-11-23 15:49 ` Pete Harlan
2005-11-23 16:42 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-11-23 12:31 Sid Boyce
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=20051123031104.GC20775@brahms.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
/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.