From: "Mark Richards" <markr@massmicro.com>
To: "'David Woodhouse'" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: RE: MTD - DOC 2000 freezes on umount
Date: Wed, 21 Jan 2004 00:51:02 -0500 [thread overview]
Message-ID: <00a001c3dfe2$93f3b090$6e01a8c0@solarwave> (raw)
In-Reply-To: <1074622256.7885.12.camel@hades.cambridge.redhat.com>
David, I ran the kernel build process and, sadly, no joy.
Here's the ending of a long string of various warnings from the compiler as
it worked through the MTD code...
gcc -D__KERNEL__ -I/usr/src/linux-2.4.24.new.mtd/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE
-DMODVERSIONS -include
/usr/src/linux-2.4.24.new.mtd/include/linux/modversions.h -nostdinc
-iwithprefix include -DKBUILD_BASENAME=write
-c -o write.o write.c
write.c: In function `jffs2_new_inode':
write.c:91: `current' undeclared (first use in this function)
write.c:91: (Each undeclared identifier is reported only once
write.c:91: for each function it appears in.)
write.c:103: `CURRENT_TIME' undeclared (first use in this function)
make[2]: *** [write.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.24.new.mtd/fs/jffs2'
make[1]: *** [_modsubdir_jffs2] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.24.new.mtd/fs'
make: *** [_mod_fs] Error 2
[root@localhost linux]#
The compile was performed on a new source tree (2.4.24) that had been
patched according to instructions and the configuration process operated as
recommended.
GCC: 2.96 20000731 (Red Hat 7.1 2.96-98) Specs from
/usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
I wonder if I should just re-install RedHat, or is there any hope
otherwise??
Mark Richards
> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: Tuesday, January 20, 2004 13:11
> To: Mark Richards
> Cc: linux-mtd@lists.infradead.org
> Subject: RE: MTD - DOC 2000 freezes on umount
>
> On Tue, 2004-01-20 at 13:04 -0500, Mark Richards wrote:
> > drivers/mtd/chips/Config.in: 14: unknown command
>
> Try 'make oldconfig' instead.
>
> --
> dwmw2
next prev parent reply other threads:[~2004-01-21 5:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 2:23 MTD - DOC 2000 freezes on umount Mark Richards
2004-01-20 13:51 ` Mark Richards
2004-01-20 14:07 ` David Woodhouse
2004-01-20 15:11 ` Mark Richards
2004-01-20 18:04 ` Mark Richards
2004-01-20 18:10 ` David Woodhouse
2004-01-20 18:32 ` Mark Richards
2004-01-21 5:51 ` Mark Richards [this message]
2004-01-20 18:20 ` Matthew S. McClintock
2004-01-20 18:22 ` David Woodhouse
2004-01-20 18:28 ` Matthew S. McClintock
2004-01-23 3:35 ` Mark Richards
[not found] <E1Aj0eB-0006rS-Bn@pentafluge.infradead.org>
2004-01-20 20:01 ` Bob Beers
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='00a001c3dfe2$93f3b090$6e01a8c0@solarwave' \
--to=markr@massmicro.com \
--cc=dwmw2@infradead.org \
--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