From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Laurent Riffard <laurent.riffard@free.fr>
Cc: reiserfs-list@namesys.com
Subject: Re: [reiser4] can't build as module with reiser4-for-2.6.17-rc4-mm1-1.patch
Date: Sat, 20 May 2006 01:37:27 +0400 [thread overview]
Message-ID: <1148074647.6390.46.camel@tribesman.namesys.com> (raw)
In-Reply-To: <e4lb65$m3n$1@sea.gmane.org>
Hello
On Fri, 2006-05-19 at 22:52 +0200, Laurent Riffard wrote:
> Hello,
>
> I just downloaded reiser4-for-2.6.17-rc4-mm1-1.patch and gave it a try.
> It seems that reiser4 won't build cleanly as a module.
>
> > CC [M] fs/reiser4/plugin/regular.o
> > LD [M] fs/reiser4/reiser4.o
> > CC drivers/base/class.o
> > LD drivers/base/built-in.o
> > LD drivers/built-in.o
> > GEN .version
> > CHK include/linux/compile.h
> > UPD include/linux/compile.h
> > CC init/version.o
> > LD init/built-in.o
> > LD .tmp_vmlinux1
> > KSYM .tmp_kallsyms1.S
> > AS .tmp_kallsyms1.o
> > LD .tmp_vmlinux2
> > KSYM .tmp_kallsyms2.S
> > AS .tmp_kallsyms2.o
> > LD vmlinux
> > SYSMAP System.map
> > SYSMAP .tmp_System.map
> > AS arch/i386/boot/setup.o
> > LD arch/i386/boot/setup
> > OBJCOPY arch/i386/boot/compressed/vmlinux.bin
> > GZIP arch/i386/boot/compressed/vmlinux.bin.gz
> > LD arch/i386/boot/compressed/piggy.o
> > LD arch/i386/boot/compressed/vmlinux
> > OBJCOPY arch/i386/boot/vmlinux.bin
> > BUILD arch/i386/boot/bzImage
> > Root device is (254, 4)
> > Boot sector 512 bytes.
> > Setup is 7183 bytes.
> > System is 1309 kB
> > Kernel: arch/i386/boot/bzImage is ready (#6)
> > Building modules, stage 2.
> > MODPOST
> > WARNING: "__copy_from_user_ll_nocache" [fs/reiser4/reiser4.ko] undefined!
> > LD [M] fs/reiser4/reiser4.ko
>
> The attached patch solved it.
Thanks for your help
> ~~
> laurent
>
prev parent reply other threads:[~2006-05-19 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 20:52 [reiser4] can't build as module with reiser4-for-2.6.17-rc4-mm1-1.patch Laurent Riffard
2006-05-19 21:37 ` Vladimir V. Saveliev [this message]
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=1148074647.6390.46.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=laurent.riffard@free.fr \
--cc=reiserfs-list@namesys.com \
/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.