EEPW论坛

问 2.6.8的内核移植yaffs文件系统,修改好了fs/Kconfig 和yaffs/Kconfig文件,fs/Makefile和fs/yaffs/Makefile也修改好了,用的是3.4.1的编译器,在进入yaffs目录compile时出现以下错误:
/usr/local/ARM//3.4.1/bin/ARM-linux-ld:fs/yaffs/built-in.o:No such file...
make[1]:*** [fs/built-in.o] ERROR 1
make:*** [fs] ERROR 2

请问built-in.o是个什么文件呢?出错之前的编译信息有几个类似于
LD fs/romfs/built-in.o的信息都能过去,就在我新建的yaffs目录出错,我需要更改什么配置选项吗? 答 1: /fs/yaffs/Kconfig#
# YAFFS Filesystem configuration
#
config YAFFS_FS
    tristate "Yet Another Flash Filing System(YAFFS) file system support"
    help
     YAFFS, for Yet Another Flash Filing System, is a filing system
     If unsure, say N.

config YAFFS_MTD_ENABLED
    bool "NAND mtd support"
    depends on YAFFS_FS
    help
      This adds the yaffs file system support for working with a NAND mtd.
      If unsure, say Y.

config YAFFS_RAM_ENABLED
    bool "yaffsram file system support"
    depends on YAFFS_FS
    help
      This adds the yaffsram file system support. Nice for testing on x86,
      but uses 2MB of RAM.  Don't enable for NAND-based targets.
      If unsure, say N.
      comment "WARNING: mtd and/or yaffsram support should be selected"
      depends on YAFFS_FS && !YAFFS_MTD_ENABLED && !YAFFS_RAM_ENABLED

config YAFFS_USE_OLD_MTD
    bool "Old mtd support"
    depends on YAFFS_FS && 0
    help
      Enable this to use the old MTD stuff that did not have yaffs support.
      You CAN use this to get around compilation problems, but the best
      thing to do is to upgrade your MTD support. You will get better speed.
      If unsure, say N.

config YAFFS_USE_NANDECC
    bool "Use ECC functions of the generic MTD-NAND driver"
    depends on YAFFS_FS
    default y
    help
      This enables the ECC functions of the generic MTD-NAND driver.
      This will not work if you are using the old mtd.
      NB Use NAND ECC does not work at present with yaffsram.
      If unsure, say Y.

config YAFFS_ECC_WRONG_ORDER
    bool "Use the same ecc byte order as Steven Hill's nand_ecc.c"
    depends on YAFFS_FS
    ---help---
      This makes yaffs_ecc.c use the same ecc byte order as
      Steven Hill's nand_ecc.c. If not set, then you get the
      same ecc byte order as SmartMedia.
      If unsure, say N.

      This is only a cosmetic option since the OS2/LONG namespace is case
      insensitive. The only major reason for this option is backward
      compatibility when moving from DOS to OS2/LONG namespace support.
      Long filenames (created by Win95) will not be affected.

      This option does not solve the problem that filenames appear
      differently under Linux and under Windows, since Windows does an
      additional conversions on the client side. You CAN achieve similar
      effects by saying Y to "Allow using of Native Language Support"
      below.

config YAFFS_USE_GENERIC_RW
    bool "Use Linux file caching layer"
    default y
    depends on YAFFS_FS
    help
      Use generic_read/generic_write for reading/writing files. This
      enables the use of the Linux file caching layer.
      If you disable this, then caching is disabled and file read/write
      is direct.

      If unsure, say Y.

config YAFFS_USE_HEADER_FILE_SIZE
    bool "Use object header size"
    depends on YAFFS_FS
    help
      When the flash is sCANned, two file sizes are constructed:
      * The size taken from the object header for the file.
      * The size figured out by sCANning the data chunks.

      If unsure, say N.
      
config YAFFS_DISABLE_CHUNK_ERASED_CHECK
    bool "Turn off debug chunk erase check"
    depends on YAFFS_FS
    default y
    help
     Enabling this turns off the test that chunks are erased in flash
     before writing to them.  This is safe, since the write verification
     will fail.  Suggest enabling the test (ie. say N)
     during development to help debug things.
     
     If unsure, say Y.

config YAFFS_SHORT_NAMES_IN_RAM
    bool "Cache short names in RAM"
    depends on YAFFS_FS
    default y
    help
      If this config is set, then short names are stored with the
      yaffs_Object.  This costs an extra 16 bytes of RAM per object,
      but makes look-ups faster.
      
      If unsure, say Y.