From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>, Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: kernel building procedure changed?
Date: Mon, 23 Feb 2009 01:07:48 +0300 [thread overview]
Message-ID: <20090222220747.GB7279@localhost> (raw)
Hi all,
I found a bit strange thing happens now --
plain
make arch/x86/kernel/head64.o
doesn't work anymore. Instead of compiling
_just_ this file I've got the following:
---
cyrill@lenovo linux-2.6.git $ make arch/x86/kernel/head64.o
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
AS arch/x86/kernel/head_64.o
VDSOSYM arch/x86/vdso/vdso-syms.lds
VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds
VDSOSYM arch/x86/vdso/vdso32-syscall-syms.lds
VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds
VDSOSYM arch/x86/vdso/vdso32-syms.lds
LD arch/x86/vdso/built-in.o
CC fs/hpfs/dnode.o
make[2]: *** [fs/hpfs/dnode.o] Interrupt
make[1]: *** [fs/hpfs] Interrupt
make: *** [fs] Interrupt
---
I've done make allyesconfig previously.
I don't understand what I'm doing wrong... :(
Really need help. The commit is:
---
commit c8f0da62a813f3ea8ceab574438afb90d428de36
Merge: b95dcd2... 8f5bd50...
Author: Ingo Molnar <mingo@elte.hu>
Date: Sun Feb 22 20:08:44 2009 +0100
manual merge of kmemcheck
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
As I understand hpfs completely unrelated to
head64.o, right?
Sam, Ingo, what I'm doing wrong? Please help :)
- Cyrill -
next reply other threads:[~2009-02-22 22:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 22:07 Cyrill Gorcunov [this message]
2009-02-22 22:13 ` kernel building procedure changed? Jesper Juhl
2009-02-22 22:16 ` Sam Ravnborg
2009-02-22 22:27 ` Jiri Slaby
2009-02-22 23:00 ` Sam Ravnborg
2009-02-22 23:15 ` Jiri Slaby
2009-02-23 7:48 ` Cyrill Gorcunov
2009-02-23 8:14 ` Cyrill Gorcunov
2009-02-22 22:28 ` Cyrill Gorcunov
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=20090222220747.GB7279@localhost \
--to=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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