public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Bernhard Priewasser <bernhard@prie.de>
To: linux-mtd@lists.infradead.org
Subject: Compiling JFFS3
Date: Wed, 10 Aug 2005 10:26:28 +0200	[thread overview]
Message-ID: <42F9BA34.6090008@prie.de> (raw)

Hello,

when trying to compile JFFS3 kernel module out-of-the-box, I get 
(pathnames stripped):

 > ~/mtd/fs/jffs3> make
 > make -C /lib/modules/2.6.11.4-21.7-default/build SUBDIRS=`pwd` 
mtd=`pwd` modules
 > make[1]: Entering directory `/usr/src/linux-2.6.11.4-21.7'
 >   CC [M]  /mtd/fs/jffs3/compr.o
 > In file included from /mtd/fs/jffs3/nodelist.h:205,
 >                  from /mtd/fs/jffs3/compr.h:27,
 >                  from /mtd/fs/jffs3/compr.c:17:
 > /mtd/fs/jffs3/debug.h: In function `jffs3_dbg_wbuf_acct_sanity_check':
 > /mtd/fs/jffs3/debug.h:366: error: structure has no member named 
`wbuf_pagesize'
 > /mtd/fs/jffs3/debug.h:366: error: structure has no member named 
`wbuf_len'
 > /mtd/fs/jffs3/debug.h:367: error: structure has no member named 
`wbuf_ofs'
 > /mtd/fs/jffs3/debug.h:367: error: structure has no member named 
`wbuf_len'
 > /mtd/fs/jffs3/debug.h:367: error: structure has no member named 
`wbuf_pagesize'
 > /mtd/fs/jffs3/debug.h:367: error: structure has no member named 
`wbuf_len'
 > make[2]: *** [/mtd/fs/jffs3/compr.o] Error 1
 > make[1]: *** [_module_/mtd/fs/jffs3] Error 2
 > make[1]: Leaving directory `/usr/src/linux-2.6.11.4-21.7'
 > make: *** [modules] Error 2

In jffs3.h, line 296ff, the write-behind and oob stuff (wbuf_* ...) is 
not added because CONFIG_JFFS3_FS_WRITEBUFFER is not defined.

Have a look at mtd/include/linux/config.h, line 38. Shouldn't
 > #define CONFIG_JFFS3_FS_WRITEBUFFER 1
be added there to consider JFFS_3_ too, not only JFFS_2_?

Regards,
Bernhard

             reply	other threads:[~2005-08-10  8:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10  8:26 Bernhard Priewasser [this message]
2005-08-10  8:38 ` Compiling JFFS3 Jörn Engel
2005-08-10  8:48   ` Bernhard Priewasser
2005-08-10  9:02     ` Artem B. Bityuckiy
2005-08-10  9:11       ` Bernhard Priewasser
2005-08-10  9:17         ` Artem B. Bityuckiy
2005-08-10  9:31           ` Bernhard Priewasser
2005-08-10  9:45             ` Artem B. Bityuckiy
2005-08-10  9:54               ` Bernhard Priewasser
2005-08-10 10:00                 ` Artem B. Bityuckiy
2005-08-10 10:05             ` Jörn Engel
2005-08-10 10:14               ` Steven Scholz
2005-08-10 10:28                 ` Bernhard Priewasser
2005-08-10 10:28                 ` Jörn Engel
2005-08-10 10:30                   ` Steven Scholz
2005-08-10 10:34                     ` Artem B. Bityuckiy
2005-08-10 10:37                       ` Steven Scholz
2005-08-10 10:42                         ` Artem B. Bityuckiy
2005-08-10 10:48                         ` Jörn Engel
2005-08-12 20:27                           ` Jared Hulbert
2005-08-12 21:26                             ` Josh Boyer
2005-08-15  9:11                             ` Jörn Engel
2005-08-10 10:36               ` Bernhard Priewasser
2005-08-10 10:45                 ` Jörn Engel
2005-08-10  8:56   ` Artem B. Bityuckiy

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=42F9BA34.6090008@prie.de \
    --to=bernhard@prie.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox