From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Jeff Dike" <jdike@addtoit.com>,
Blaisorblade <blaisorblade@yahoo.it>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: [PROBLEM] uml doesn't compile on i386
Date: Fri, 23 Nov 2007 10:52:06 +0200 [thread overview]
Message-ID: <84144f020711230052h2d0b8af8radbdf1d7b08a57e3@mail.gmail.com> (raw)
Hi,
Current git head doesn't compile. Looks like fall-out from the x86 merge?
penberg@haji:~/src/linux/uml-2.6$ make ARCH=um
SYMLINK arch/um/include/kern_constants.h
SYMLINK arch/um/include/sysdep
make[1]: `arch/um/sys-i386/user-offsets.s' is up to date.
CHK arch/um/include/user_constants.h
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CC arch/um/kernel/asm-offsets.s
In file included from include/asm/arch/atomic.h:2,
from include/asm/atomic.h:9,
from include/linux/spinlock.h:333,
from include/linux/seqlock.h:29,
from include/linux/time.h:8,
from include/linux/timex.h:57,
from include/linux/sched.h:53,
from arch/um/include/sysdep/kernel-offsets.h:2,
from arch/um/kernel/asm-offsets.c:1:
include/asm/arch/atomic_32.h: In function 'atomic_add_unless':
include/asm/arch/atomic_32.h:237: error: 'struct cpuinfo_um' has no
member named 'x86'
In file included from include/asm/rwsem.h:4,
from include/linux/rwsem.h:24,
from include/linux/mm_types.h:11,
from include/linux/sched.h:60,
from arch/um/include/sysdep/kernel-offsets.h:2,
from arch/um/kernel/asm-offsets.c:1:
include/asm/arch/rwsem.h: In function '__down_write_trylock':
include/asm/arch/rwsem.h:165: error: 'struct cpuinfo_um' has no member
named 'x86'
make[1]: *** [arch/um/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
Pekka
next reply other threads:[~2007-11-23 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 8:52 Pekka Enberg [this message]
2007-11-23 10:13 ` WANG Cong
2007-11-23 10:32 ` Pekka Enberg
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=84144f020711230052h2d0b8af8radbdf1d7b08a57e3@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.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®