From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-git latest build broken on UP x86-64
Date: Wed, 23 Nov 2005 12:31:25 +0000 [thread overview]
Message-ID: <4384611D.5020808@blueyonder.co.uk> (raw)
Andi Kleen wrote:
> Works for me with -git2 and defconfig changed to UP. config please
and last changeset.
>
> -Andi
SuSE 10.0 x86_64 UP 2.6.15-rc2-git3. As previously posted, with -git2 a
successful build depended on ext3 being configured, but this error was
not seen.
CC arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/main.o
arch/x86_64/kernel/../../i386/kernel/cpu/mtrr/main.c: In function
‘set_mtrr’:
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[1]: *** [arch/x86_64/kernel/../../i386/kernel/cpu/mtrr] Error 2
make: *** [arch/x86_64/kernel] Error 2
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next reply other threads:[~2005-11-23 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 12:31 Sid Boyce [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2005-11-23 15:49 ` Pete Harlan
2005-11-23 16:42 ` Andi Kleen
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=4384611D.5020808@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.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.