From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.5.72 for ia64 released
Date: Fri, 20 Jun 2003 11:38:05 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105610921423687@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105605890319553@msgid-missing>
David Mosberger <davidm@napali.hpl.hp.com> writes:
|> A patch to make 2.5.72 work on ia64 is now available in the usual
|> place:
|>
|> ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/v2.5/
|> linux-2.5.72-ia64-030619.diff.bz2
A generic kernel does not compile. Any idea how to fix?
CC arch/ia64/sn/io/sgi_io_sim.o
In file included from include/asm/nodedata.h:17,
from include/asm/sn/sn_cpuid.h:20,
from include/asm/sn/sn_sal.h:17,
from arch/ia64/sn/io/sgi_io_sim.c:13:
include/asm/mmzone.h:51:1: warning: "kern_addr_valid" redefined
In file included from include/asm/uaccess.h:36,
from include/asm/sn/sgi.h:17,
from arch/ia64/sn/io/sgi_io_sim.c:12:
include/asm/pgtable.h:191:1: warning: this is the location of the previous definition
In file included from include/asm/sn/sn_cpuid.h:20,
from include/asm/sn/sn_sal.h:17,
from arch/ia64/sn/io/sgi_io_sim.c:13:
include/asm/nodedata.h:27: error: `NR_NODES' undeclared here (not in a function)
include/asm/nodedata.h:28: error: `NR_BANKS' undeclared here (not in a function)
include/asm/nodedata.h:29: error: `NR_NODES' undeclared here (not in a function)
include/asm/nodedata.h:30: error: `NR_BANKS' undeclared here (not in a function)
In file included from include/asm/sn/sn_cpuid.h:21,
from include/asm/sn/sn_sal.h:17,
from arch/ia64/sn/io/sgi_io_sim.c:13:
include/asm/sn/pda.h:59: error: `NR_NODES' undeclared here (not in a function)
include/asm/sn/pda.h:63: confused by earlier errors, bailing out
make[2]: *** [arch/ia64/sn/io/sgi_io_sim.o] Error 1
make[1]: *** [arch/ia64/sn/io] Error 2
make: *** [arch/ia64/sn] Error 2
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-06-20 11:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 21:39 2.5.72 for ia64 released David Mosberger
2003-06-20 11:38 ` Andreas Schwab [this message]
2003-06-20 17:11 ` Jesse Barnes
2003-06-20 17:47 ` Sam Ravnborg
2003-06-20 18:01 ` David Mosberger
2003-06-20 18:35 ` Jesse Barnes
2003-06-20 18:41 ` David Mosberger
2003-06-20 18:45 ` Jesse Barnes
2003-06-20 18:49 ` David Mosberger
2003-06-20 18:50 ` Jesse Barnes
2003-06-20 18:53 ` Jesse Barnes
2003-06-20 19:02 ` David Mosberger
2003-06-20 19:07 ` Jesse Barnes
2003-06-20 19:44 ` Andreas Schwab
2003-06-20 19:49 ` Jesse Barnes
2003-06-20 19:51 ` Andreas Schwab
2003-06-20 19:56 ` Jesse Barnes
2003-06-20 20:03 ` Alex Tsariounov
2003-06-20 20:06 ` David Mosberger
2003-06-20 20:25 ` Andreas Schwab
2003-06-20 20:28 ` Jesse Barnes
2003-06-20 20:34 ` David Mosberger
2003-06-20 20:39 ` Jesse Barnes
2003-06-20 20:40 ` Andreas Schwab
2003-06-20 20:50 ` David Mosberger
2003-06-20 20:51 ` Sam Ravnborg
2003-06-20 21:04 ` Jack Steiner
2003-06-20 21:06 ` David Mosberger
2003-06-20 21:21 ` Jesse Barnes
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=marc-linux-ia64-105610921423687@msgid-missing \
--to=schwab@suse.de \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox