Le lun 17/05/2004 �9:06, Ling Hwa Hing a �it : > hi all, > I'd managed to build the RPM package with multipath-tools-0.1.9. and now when i try to execute the #> multipath or with any other switches, the program gave me Segmentation Fault error on my console. and my RPM package build without problem. > > During the compilation, there are lots of warning which complaint by gcc. below are the example:- > > make[3]: Entering directory `/tmp/multipath-tools-0.1.9/klibc/klibc' > gcc -Wp,-MD,syscalls/.__brk.d -mregparm=3 -DREGPARM -march=i386 -Os -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -I../klibc -I../klibc/arch/i386/include -I../klibc/include/bits32 -D__KLIBC__ -DBITSIZE=32 -I../klibc/include -I../linux/include -W -Wall -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Winline -c -o syscalls/__brk.o syscalls/__brk.c > In file included from ../klibc/include/unistd.h:9, > from ../klibc/syscommon.h:28, > from syscalls/__brk.c:1: > ../klibc/include/klibc/compiler.h:82:1: warning: "__attribute_pure__" redefined > In file included from ../linux/include/linux/uio.h:4, > from ../klibc/include/sys/uio.h:10, > from ../klibc/syscommon.h:23, > from syscalls/__brk.c:1: > ../linux/include/linux/compiler.h:94:1: warning: this is the location of the previous definition > In file included from ../klibc/include/unistd.h:9, > from ../klibc/syscommon.h:28, > from syscalls/__brk.c:1: > ../klibc/include/klibc/compiler.h:101:1: warning: "__attribute_const__" redefined > In file included from ../linux/include/linux/uio.h:4, > from ../klibc/include/sys/uio.h:10, > from ../klibc/syscommon.h:23, > from syscalls/__brk.c:1: > > could it be klibc cousing this? how can I provide you all more information instead of the statement above? > I'm ain't good enugh to deal with this..... sigh... > Yes, these messages come from klibc anyway, I just compiled on a Celeron, Fedora core 2, and it gives no segfault even if I also see these warnings. so please send the 'strace multipath -v' output, and give a little more detail about your SAN environment (hw models, scsi strings, ...). regards, cvaroqui