[sheepdog] Issues about setup

[hujianyang]

On 2015/1/16 17:40, Hitoshi Mitake wrote:
> 
> Hi Hu,
> 
> At Fri, 16 Jan 2015 16:43:22 +0800,
> hujianyang wrote:
>>
>> Hi Hitoshi,
>>
>> I'm a learner of sheepdog. Here is two issues about setting
>> up sheepdog in my environment.
>>
>> 1) invalid option '-d' in README
>>
>> """
>> To set up a 3 node cluster using local driver in one liner bash with debug mode:
>>
>>       $ mkdir /path/to/store
>>       $ for i in 0 1 2; do sheep -c local -d /path/to/store/$i -z $i -p 700$i;sleep 1;done
>> """
>>
>> but:
>>
>>       $ sheep -c local -d /mnt/store/0 -z 0 -p 7000
>>       sheep: invalid option -- 'd'
>>       Try 'sheep --help' for more information.
>>
>> Seems '-d' is removed so maybe README file should be updated?
> 
> As you noticed, -d is removed already. And the README file is very
> outdated. I have to update the file but I'm busy in these days. I'll
> do it later, but if you have time, could you post a patch for updating
> README? If you can help us, it is very helpful :)
> 

I'd like to, but I think I should know more about this filesystem
first.

Give me some time.

>>
>> 2) compile error in version v0.9.0+
>>
>> When compile sheepdog v0.9.0+, I met a lots of error messages
>> below:
>>
>> yasm -f elf64 -D NDEBUG -Ierasure_code -Iinclude -o bin/gf_vect_mul_sse.o erasure_code/gf_vect_mul_sse.asm
>>   ---> Building erasure_code/gf_vect_mul_avx.asm
>> yasm -f elf64 -D NDEBUG -Ierasure_code -Iinclude -o bin/gf_vect_mul_avx.o erasure_code/gf_vect_mul_avx.asm
>>   ---> Building erasure_code/gf_vect_dot_prod_sse.asm
>> yasm -f elf64 -D NDEBUG -Ierasure_code -Iinclude -o bin/gf_vect_dot_prod_sse.o erasure_code/gf_vect_dot_prod_sse.asm
>> erasure_code/gf_vect_mul_avx.asm:116: instruction expected after label
>> erasure_code/gf_vect_mul_avx.asm:117: instruction expected after label
>> erasure_code/gf_vect_mul_avx.asm:118: redefinition of `vmovdqu'
>> erasure_code/gf_vect_mul_avx.asm:117: `vmovdqu' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:121: instruction expected after label
>> erasure_code/gf_vect_mul_avx.asm:122: redefinition of `vmovntdqa'
>> erasure_code/gf_vect_mul_avx.asm:121: `vmovntdqa' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:125: instruction expected after label
>> erasure_code/gf_vect_mul_avx.asm:126: redefinition of `vpand'
>> erasure_code/gf_vect_mul_avx.asm:125: `vpand' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:127: instruction expected after label
>> erasure_code/gf_vect_mul_avx.asm:128: redefinition of `vpsraw'
>> erasure_code/gf_vect_mul_avx.asm:127: `vpsraw' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:129: redefinition of `vpand'
>> erasure_code/gf_vect_mul_avx.asm:125: `vpand' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:130: redefinition of `vpand'
>> erasure_code/gf_vect_mul_avx.asm:125: `vpand' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:131: instruction expected after label
>> erasure_code/gf_vect_mul_avx.asm:132: redefinition of `vpshufb'
>> erasure_code/gf_vect_mul_avx.asm:131: `vpshufb' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:133: redefinition of `vpshufb'
>> erasure_code/gf_vect_mul_avx.asm:131: `vpshufb' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:134: redefinition of `vpshufb'
>> erasure_code/gf_vect_mul_avx.asm:131: `vpshufb' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:135: instruction expected after label
>> erasure_code/gf_vect_mul_avx.asm:136: redefinition of `vpxor'
>> erasure_code/gf_vect_mul_avx.asm:135: `vpxor' previously defined here
>> erasure_code/gf_vect_mul_avx.asm:137: instruction expected after label
>> erasure_code/gf_vect_mul_avx.asm:138: redefinition of `vmovntdq'
>> erasure_code/gf_vect_mul_avx.asm:137: `vmovntdq' previously defined here
>> make[2]: *** [bin/gf_vect_mul_avx.o] Error 1
>> make[2]: *** Waiting for unfinished jobs....
>> make[2]: Leaving directory `/opt/sheepdog/lib/isa-l'
>> make[1]: *** [libisa.a] Error 2
>> make[1]: *** Waiting for unfinished jobs....
>>
>> I switch to use v0.8.3 and it's OK.
>>
>> I'm not sure if it's a real problem or I miss something. I'd
>> like to show you the software version of my environment if it
>> is really needed.
>>
> 
> Hmm, could you show your yasm version? My yasm (1.2.0) can build
> current master branch with no problems.

# yasm --version
yasm 0.6.2.1985
Compiled on Feb 23 2009.
Copyright (c) 2001-2007 Peter Johnson and other Yasm developers.
Run yasm --license for licensing overview and summary.


I'm running on a very old SUSE11sp2.

Thanks for your replay~!
Hu