From: Peter Lieverdink <lkml@cafuego.net>
To: jdike@karaya.com
Cc: linux-kernel@vger.kernel.org
Subject: UM Linux 2.6.0-test5 (-mm2) fails to build
Date: Tue, 16 Sep 2003 11:49:30 +1000 [thread overview]
Message-ID: <5.1.0.14.2.20030916113642.00b4d538@caffeine.cc.com.au> (raw)
Hi Jeff,
I'm having a play with UML (on Debian testing, gcc 2.95.4, x86 box) and the
um kernel fails to build. Same on Debian unstable with gcc-3.3. Looks like
either a missing include or changed struct. (or both) My experience extends
about as far as trying to include <asm/cache.h> (which defines
CONFIG_X86_L1_CACHE_SHIFT) in "include/linux/sched.h" but that didn't work,
oh well :-)
Hopefully a more or less useful bugreport.
- Peter.
--
make -f scripts/Makefile.build obj=arch/um/util
gcc -o arch/um/util/mk_task_user.o -c arch/um/util/mk_task_user.c
CC arch/um/util/mk_task_kern.o
In file included from include/asm/thread_info.h:13,
from include/linux/thread_info.h:21,
from include/linux/spinlock.h:12,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from arch/um/util/mk_task_kern.c:1:
include/asm/processor.h:66: `CONFIG_X86_L1_CACHE_SHIFT' undeclared here
(not in a function)
include/asm/processor.h:66: requested alignment is not a constant
In file included from include/linux/gfp.h:4,
from include/linux/slab.h:15,
from include/linux/percpu.h:4,
from include/linux/sched.h:31,
from arch/um/util/mk_task_kern.c:1:
include/linux/mmzone.h:60: `CONFIG_X86_L1_CACHE_SHIFT' undeclared here (not
in a function)
include/linux/mmzone.h:60: requested alignment is not a constant
arch/um/util/mk_task_kern.c: In function `main':
arch/um/util/mk_task_kern.c:13: structure has no member named `regs'
make[1]: *** [arch/um/util/mk_task_kern.o] Error 1
make: *** [arch/um/util] Error 2
next reply other threads:[~2003-09-16 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 1:49 Peter Lieverdink [this message]
2003-09-16 5:54 ` Bryan O'Sullivan
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=5.1.0.14.2.20030916113642.00b4d538@caffeine.cc.com.au \
--to=lkml@cafuego.net \
--cc=jdike@karaya.com \
--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 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®