From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: GENERIC still failing?
Date: Wed, 15 Oct 2003 00:22:05 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106617734007194@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106617635106445@msgid-missing>
On Tue, Oct 14, 2003 at 05:12:17PM -0700, jbarnes wrote:
> On Tue, Oct 14, 2003 at 05:05:14PM -0700, David Mosberger wrote:
> > According to this page:
> >
> > http://www.gelato.unsw.edu.au/kerncomp/
> >
> > GENERIC builds are still failing:
> >
> > gcc -Wp,-MD,fs/ext2/.balloc.o.d -nostdinc -iwithprefix include -D__KERNEL__ -Iinclude -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -ffixed-r13 -mfixed-rangeñ2-f15,f32-f127 -falign-functions2 -frename-registers -fomit-frame-pointer -mconstant-gp -DKBUILD_BASENAMEºlloc -DKBUILD_MODNAME=ext2 -c -o fs/ext2/balloc.o fs/ext2/balloc.c
> > arch/ia64/sn/kernel/setup.c:94: error: `MAX_PHYSNODE_ID' undeclared here (not in a function)
> > arch/ia64/sn/kernel/setup.c:94: error: conflicting types for `physical_node_map'
> > include/asm/sn/sn_cpuid.h:126: error: previous declaration of `physical_node_map'
> >
> > Anybody care to send me a fix for this?
Looks like CONFIG_NUMA and CONFIG_DISCONTIGMEM are missing from the
config being built. A generic kernel won't work without them.
Jesse
next prev parent reply other threads:[~2003-10-15 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 0:05 GENERIC still failing? David Mosberger
2003-10-15 0:12 ` Jesse Barnes
2003-10-15 0:22 ` Jesse Barnes [this message]
2003-10-15 0:56 ` David Mosberger
2003-10-15 0:57 ` David Mosberger
2003-10-15 2:15 ` Ian Wienand
2003-10-15 2:40 ` Randy.Dunlap
2003-10-15 3:03 ` Jesse Barnes
2003-10-15 11:24 ` Matthew Wilcox
2003-10-15 23:14 ` Ian Wienand
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-106617734007194@msgid-missing \
--to=jbarnes@sgi.com \
--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 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.