I managed to solve the problem by updating the boost version used to 1_64_0
This resulted in a SUCCESS status!


On Sat, 30 Jan 2021 at 14:26, Marwa Gaser <marwaga...@gmail.com> wrote:

> Now when I tried to compile mosesdecoder with boost, cmph, xmlrpc, and
> irstlm using the below command on windows *wsl*:
>
>  ./bjam --with-boost=/c/Users/HP/SMT_trial1/boost_1_55_0
> --with-cmph=/c/Users/HP/SMT_trial1/cmph-2.0
> --with-irstlm=/c/Users/HP/SMT_trial1/irstlm-5.80.08
> --with-xmlrpc-c=/c/Users/HP/SMT_trial1/xmlrpc-c-1.33.14 -j7
>
> I got the error attached. Is that because of the difference in file ending
> in linux and windows?
>
> On Fri, 29 Jan 2021 at 16:10, Hieu Hoang <hieuho...@gmail.com> wrote:
>
>> the unit tests are failing, but the compile seems to have succeeded.
>>
>> I get a similar error compiling on a WSL2 environment but i know the
>> compile itself has succeeded:
>>
>>     No such file or directory in
>> /mnt/c/Users/hihoan/workspace/github/mosesdecoder/test.binaryDlFBwO
>> (deleted) while resizing to 0 bytes Byte: 62
>>
>> This is because the Windows file system doesn't support some reporting
>> functionality,
>>
>> Check that your disk is not full, check that bin/moses exists. If it
>> does, then just ignore the unit test errors.
>>
>>
>> On Fri Jan 29, 21 12:12 AM, Marwa Gaser wrote:
>>
>> Dear Moses Support Team,
>>
>> I am using *wsl *on windows to run mosesdecoder for the first time.
>>
>> What I did is that I cloned the mosesdecoder repo. Then I opened the cmd
>> inside the mosesdecoder repo and ran the following command *bjam -j4 
>> *However,
>> I got the error attached in the file.
>>
>> Thank you in advance.
>>
>> Respectfully,
>> Marwa
>>
>> _______________________________________________
>> Moses-support mailing 
>> listMoses-support@mit.eduhttp://mailman.mit.edu/mailman/listinfo/moses-support
>>
>> --
>> Hieu Hoanghttp://statmt.org/hieu
>>
>>
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to