All of lore.kernel.org
 help / color / mirror / Atom feed
From: data <data@uniquemodem.com>
To: linux-mtd@lists.infradead.org
Subject: mtdblock.c cannot compile under Linux 2.2.x
Date: Wed, 17 Oct 2001 21:17:21 +0800	[thread overview]
Message-ID: <3BCD84E1.4DD484A6@uniquemodem.com> (raw)

Hi David,

Thanks for your information for fixing the parsing error in chipreg.c. I
have gone through another step and the compilation fail in the
mtdblock.c area. I don't know what goes wrong. Could you please have a
look at our problem? I have attacked the log for your reference.


Build log:

make all_targets
make[3]: Entering directory `/home/root/linux-2.2.18/drivers/mtd'
cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce
-m386 -DCPU=386   -c -o mtdcore.o mtdcore.c
cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce
-m386 -DCPU=386   -c -o mtdchar-compat.o mtdchar-compat.c
cc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce
-m386 -DCPU=386   -c -o mtdblock.o mtdblock.c
mtdblock.c: In function `mtdblock_ioctl':
mtdblock.c:544: impossible register constraint in `asm'
mtdblock.c:544: impossible register constraint in `asm'
mtdblock.c:544: impossible register constraint in `asm'
mtdblock.c:563: confused by earlier errors, bailing out
make[3]: *** [mtdblock.o] Error 1
make[3]: Leaving directory `/home/root/linux-2.2.18/drivers/mtd'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/home/root/linux-2.2.18/drivers/mtd'
make[1]: *** [_subdir_mtd] Error 2
make[1]: Leaving directory `/home/root/linux-2.2.18/drivers'
make: *** [_dir_drivers] Error 2
[root@localhost linux]#

Build: End

In order to let me carry forward the compilation process, I have change
our selection to drop the MTD_BLOCK_DEVICE option. The compilation has
passed the mtd but fail again at kernel build. I have also attached the
console log for your reference.

Could you please llet me know what goes wrong for the compilation
process?

Thanks and regards,

Jimmy Chun


Build Log:

make[2]: Leaving directory `/home/root/linux-2.2.18/arch/i386/lib'
make[1]: Leaving directory `/home/root/linux-2.2.18/arch/i386/lib'
cc -D__KERNEL__ -I/usr/src/linux/include -E -C -P
-I/usr/src/linux/include -imacros
/usr/src/linux/include/asm-i386/page_offset.h -Ui386
arch/i386/vmlinux.lds.S >arch/i386/vmlinux.lds
ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
init/version.o \
 --start-group \
 arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o
fs/fs.o ipc/ipc.o \
 fs/filesystems.a \
 net/network.a \
 drivers/block/block.a drivers/char/char.o drivers/misc/misc.a
drivers/net/net.a drivers/pci/pci.a drivers/video/video.a \
 /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a
/usr/src/linux/arch/i386/lib/lib.a \
 --end-group \
 -o vmlinux
init/main.o: In function `do_basic_setup':
init/main.o(.text.init+0xec7): undefined reference to `init_mtd'
fs/fs.o: In function `filesystem_setup':
fs/fs.o(.text.init+0x533): undefined reference to `init_jffs_fs'
make: *** [vmlinux] Error 1
[root@localhost linux]#


Build END

             reply	other threads:[~2001-10-17 13:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-17 13:17 data [this message]
2001-10-17 13:23 ` mtdblock.c cannot compile under Linux 2.2.x David Woodhouse
2001-10-18 13:32   ` data
2001-10-18 13:36     ` David Woodhouse
2001-10-19 13:56   ` Problem on recognise the CFI flash chip on SC520CDP data
2001-10-19 13:59     ` David Woodhouse
2001-10-24 13:44   ` Compilation problem on linux-2.4.6 with patch 2.4.6pre3 data

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=3BCD84E1.4DD484A6@uniquemodem.com \
    --to=data@uniquemodem.com \
    --cc=linux-mtd@lists.infradead.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.