[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Reiserfs

I have no idea if reiserfs runs on sparc or not, I know they're just now 
getting the Alpha port in working order.

The error you're getting is related to a define that they have gotten into 
the errno.h for i386 but no other arches yet, at the bottom of 
include/asm/errno.h add an entry like:

#define EHASHCOLLISION    127   /* reiserfs hash collision */

and that should fix that error. Eventually when reiserfs is in the kernel 
(around 2.4.1) this should be taken care of.


> I tried to compile a 2.2.18 with reiserfs-support. This happens:
> make[3]: Entering directory `/usr/src/linux-2.4.0/fs/reiserfs'         
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
> \ -fomit-frame-pointer -fno-strict-aliasing -m32 -pipe -mno-fpu \
> -fcall-used-g5 -fcall-used-g7    -c -o namei.o namei.c
> In file included from namei.c:8:
> /usr/src/linux/include/linux/reiserfs_fs.h: In function
> `find_next_nonzero_bit':
> /usr/src/linux/include/linux/reiserfs_fs.h:2043: warning: implicit
> declaration   of function `generic_ffs'
> namei.c: In function `reiserfs_add_entry':
> namei.c:474: `EHASHCOLLISION' undeclared (first use in this function)
> namei.c: In function `reiserfs_mkdir':
> namei.c:646: warning: comparison is always false due to limited range
> of data \  type 
> Well, are there any reports whether reiserfs runs on Sparc/32bit at
> all?  Does it normally compile, or am I doing something wrong (wrong
> header-file  somewhere)?
> Peter
> -- 
> "Any good Unix security engineer can clean up any Unix box. But I'm not
>  sure there are people even within Microsoft who know how to clean up 
>  an NT box." -- Michael Zbouray
> --  
> To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org

Reply to: