Re: [Moses-support] mgiza signal 11 coredump

2016-01-20 Thread Hieu Hoang
oops. Thanks for the fix! Hieu Hoang http://www.hoang.co.uk/hieu On 20 January 2016 at 15:31, Matjaz Rihtar wrote: > I've found the reason for this coredump: USER environment variable not > set, bug already reported on Feb 2, 2015 > https://github.com/moses-smt/mgiza/issues/4 > Said to be fixed

Re: [Moses-support] mgiza signal 11 coredump

2016-01-20 Thread Matjaz Rihtar
I've found the reason for this coredump: USER environment variable not set, bug already reported on Feb 2, 2015 https://github.com/moses-smt/mgiza/issues/4 Said to be fixed in the next few days ;-), which can now be easily done if my pull request #7 on github:moses-smt/mgiza is merged into master

[Moses-support] mgiza signal 11 coredump

2016-01-16 Thread Matjaz Rihtar
Hello! I am trying to establish a working version of Moses for the purposes of our project. I followed guidelines from the Moses Web pages (Baseline System, ...) and it was mostly successful, except for the usage of mgiza. History of what I did: My System: virtual machine with Ubuntu 14.04 x64,