compile errors with daily snapshots

compile errors with daily snapshots

[Michael Howard]

Hello,

I've been grabbing the daily snapshots for a couple of weeks now and 
keep seeing the following error:

fs/jffs2/write.c: In function `jffs2_write_dnode':
fs/jffs2/write.c:95: error: storage size of `vecs' isn't known
fs/jffs2/write.c:95: warning: unused variable `vecs'
fs/jffs2/write.c: In function `jffs2_write_dirent':
fs/jffs2/write.c:236: error: storage size of `vecs' isn't known
fs/jffs2/write.c:236: warning: unused variable `vecs'
make[2]: *** [fs/jffs2/write.o] Error 1
make[1]: *** [fs/jffs2] Error 2
make: *** [fs] Error 2


Is anyone else getting this?  I've tried patching 2.4.23 and 2.6.7 with 
the same results.  Any help would be much appreciated.

Thanks
Mike

Re: compile errors with daily snapshots

[Josh Boyer]

On Tue, 2004-08-17 at 15:33, Michael Howard wrote:
> Hello,
> 
> I've been grabbing the daily snapshots for a couple of weeks now and 
> keep seeing the following error:
> 
> fs/jffs2/write.c: In function `jffs2_write_dnode':
> fs/jffs2/write.c:95: error: storage size of `vecs' isn't known
> fs/jffs2/write.c:95: warning: unused variable `vecs'
> fs/jffs2/write.c: In function `jffs2_write_dirent':
> fs/jffs2/write.c:236: error: storage size of `vecs' isn't known
> fs/jffs2/write.c:236: warning: unused variable `vecs'
> make[2]: *** [fs/jffs2/write.o] Error 1
> make[1]: *** [fs/jffs2] Error 2
> make: *** [fs] Error 2
> 
> 
> Is anyone else getting this?  I've tried patching 2.4.23 and 2.6.7 with 
> the same results.  Any help would be much appreciated.

dwmw2 updated CVS to merge with Linus, so you need 2.6.8-rc1 or greater
for the snapshots to work with a 2.6 kernel.  Actually, because of the
merge 2.6.8 should be fairly close to CVS anyway.

No comment on 2.4 support... ;)

As for your specific error, Al Viro moved struct kvec into
include/linux/uio.h during some sparse annotation cleanup.  That in
itself wouldn't be hard to fix, but you also need the symlink patches Al
did for jffs2 to work.  That's a larger patch kit, so it's probably
simpler to update to 2.6.8.1.

josh