From: "James Schettine" <james@telos-systems.com>
To: linux-mtd@lists.infradead.org
Subject: trouble compiling mkfs.jffs2
Date: Fri, 14 Sep 2001 14:20:02 -0400 [thread overview]
Message-ID: <fc.000f680100283f75000f680100283f75.283ff2@telos-systems.com> (raw)
JFFS2 is working great on my embedded arm processor.
(Great work everybody!)
I have started out with a pre-built root image I grabbed
from others working on handhelds, and they have set
the erase block size to 0x40000 and mine needs to be
0x20000. Question #1... does this only affect the
overhead/optimal use or will I actually run into problems
if I run this over a long period.
In order to re-flash my embedded root filesystem with
the correct erase block size, I have transferred all files
to my desktop system (an older Debian 2.2) and read up
on using mkfs.jffs2. I couldn't find a pre-compiled binary
in a quick and lazy search so I grabbed the cvs tree,
cd util, and make mkfs.jffs2. (did the configure thing too,
but that didn't fix this problem.)
I'm getting problems with size_t undefined in linux/string.h
(I can't believe it doesn't include what it needs !), and
patching around that I get conflicts between linux/string.h
and asm/string.h
Then it struck me that as a user-land utility application,
we shouldn't need to get TOO intimate with the kernel.
After all, I am cross-building my filesystem. The more
you ask about the host kernel, the more wrong you'll
be when you get to the target kernel.
Has anyone else had these troubles/got a work-around.
It's not a good time to be upgrading this particular
system right now.
next reply other threads:[~2001-09-14 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 18:20 James Schettine [this message]
2001-09-15 19:12 ` trouble compiling mkfs.jffs2 Jörn Engel
2001-09-17 13:06 ` Re(2): " James Schettine
2001-09-17 13:51 ` David Woodhouse
2001-09-17 14:48 ` Joakim Tjernlund
2001-09-17 14:53 ` David Woodhouse
2001-09-17 15:17 ` Joakim Tjernlund
2001-09-17 15:20 ` David Woodhouse
2001-09-17 15:24 ` Joakim Tjernlund
2001-09-17 18:57 ` Erik Andersen
2001-09-17 18:16 ` jffs vs. jffs2 & new code Jörn Engel
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=fc.000f680100283f75000f680100283f75.283ff2@telos-systems.com \
--to=james@telos-systems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox