Moses-support Digest, Vol 97, Issue 40

Send Moses-support mailing list submissions to
moses-support@mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu

You can reach the person managing the list at
moses-support-owner@mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."


Today's Topics:

1. Re: The decoder died with 'Segmentation fault' (Huei-Chi Lin)
2. Re: Cannot install moses, bjam failes due to not finding
boost libraries (lib64 in particular) (Hieu Hoang)


----------------------------------------------------------------------

Message: 1
Date: Sun, 16 Nov 2014 19:29:34 +0100
From: Huei-Chi Lin <lin@lium.univ-lemans.fr>
Subject: Re: [Moses-support] The decoder died with 'Segmentation
fault'
To: Hieu Hoang <Hieu.Hoang@ed.ac.uk>
Cc: moses-support <moses-support@mit.edu>
Message-ID: <5468ED0E.5000409@lium.univ-lemans.fr>
Content-Type: text/plain; charset="utf-8"

Hi,

I got similar message from the backtrack by running previous moses. I
will try the newest moses to see if I still have the Segmentation fault
problem.

thanks,
Huei-Chi Lin

Le 16/11/2014 16:45, Hieu Hoang a ?crit :
> can you provide the exact command you ran, and the moses.ini file you
> used.
>
> There was a race condition in the decoder which caused random
> segfaults when multithreading was used
> https://github.com/moses-smt/mosesdecoder/issues/76
> However, the segfaults are rare.
>
> This was fixed a few weeks ago. Maybe update the moses code and try
> running again. If it's still a problem, let us know again and i'll try
> & see what the problem is
>
> On 12 November 2014 14:07, Huei-Chi Lin <lin@lium.univ-lemans.fr
> <mailto:lin@lium.univ-lemans.fr>> wrote:
>
> Hello,
>
> When I ran mert-moses.pl <http://mert-moses.pl> of 2014-05-29
> version, the messages
> 'Segmentation fault' and 'The decoder died.' were written into the log
> file. This problem occurs randomly, if the mert are run several times.
> Running mert within a backtracking debugger, the messages are as
> follows:
>
> (gdb) exec-file /path/to/the/directory/bin/moses
> (gdb) r "mert options"
>
> Translating line 2340 in thread id 140734307309312
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fff44e56700 (LWP 22396)]
> 0x00000000005e6625 in ?? ()
>
> Could someone help me to resolve this problem, thanks?
>
> best regards,
> Huei-Chi Lin
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu <mailto:Moses-support@mit.edu>
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
>
>
> --
> Hieu Hoang
> Research Associate
> University of Edinburgh
> http://www.hoang.co.uk/hieu
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20141116/07d9c534/attachment-0001.htm

------------------------------

Message: 2
Date: Sun, 16 Nov 2014 18:32:34 +0000
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] Cannot install moses, bjam failes due to
not finding boost libraries (lib64 in particular)
To: Daniel Seita <takeshidanny@gmail.com>
Cc: moses-support@mit.edu
Message-ID: <5468EDC2.2040202@gmail.com>
Content-Type: text/plain; charset="utf-8"


On 16/11/14 18:27, Daniel Seita wrote:
> Sorry if I wasn't clear in my last email. I did run ./boostrap.sh
> first before running ./b2.
>
> And with regards to tagged vs system, the discussion you linked to
> seems to imply that the system name is the default. But by running
> "brew install boost", which seems to be the standard way to get boost
> on Macs, I get the tagged file names, e.g., libboost_thread-mt.a, in
> my boost directories. So how can the system be the default, but more
> importantly, how can I "have the system format"?
i don;t know how to get homebrew to do that. I would personally put my
effort into compiling my own boost lib. I wrote the instructions while i
was still using a mac so I know that it works

> Running ./bjam with --layout=tagged or --layout=system resulted in the
> same errors as in my first post.
>
> Thanks,
> Daniel
>
>
> On Sun, Nov 16, 2014 at 9:49 AM, Hieu Hoang <hieuhoang@gmail.com
> <mailto:hieuhoang@gmail.com>> wrote:
>
>
> On 16/11/14 17:41, Daniel Seita wrote:
>> Thanks for the assistance. Unfortunately, I am still running into
>> problems. First, to answer the questions about libboost_thread, I
>> have the following files:
>>
>> /usr/local/Cellar/boost/1.56.0/lib/libboost_thread-mt.a
>> /usr/local/Cellar/boost/1.56.0/lib/libboost_thread-mt.dylib
>>
>> I'm not sure what the difference of libboost_thread-mt.a versus
>> libboost_thread.a means.
> -mt.a is called a tagged name.
> .a is called a system name
> It's just an annoying file name difference. Moses changed from
> using tagged to using system a few months ago so you must have the
> system format.
> https://www.mail-archive.com/moses-support%40mit.edu/msg10653.html
>>
>> But in any case, I just uninstalled boost and tried to install it
>> again using your way and the sourceforge link. Notice that this
>> installs boost *1.55* instead of 1.56. I installed boost, put it
>> in my home directory, and then untarred it, and boostrapped it.
>> But then this command fails:
>>
>> ./b2 -j8 --prefix=$PWD --libdir=$PWD/lib64 --layout=system
>> link=static install || echo failure
>>
> it should work with v.1.55 and 1.56
>> There were so many errors that this gave me that I'm not sure how
>> to interpret them, so I've attached it in a log file in case it
>> helps. I got the log by running:
>>
>> ./b2 -j8 --prefix=$PWD --libdir=$PWD/lib64 --layout=system
>> link=static install >> boost_build.log
>>
> read the doc carefully. You must run this 1st
> ./bootstrap.sh
>
>> And in any case I do not see any file that contains
>> "libboost_thread" in it in the lib64 directory. I am not sure
>> what the issue is with boost.
>>
>> Thanks,
>> Daniel
>>
>>
>> On Sun, Nov 16, 2014 at 8:09 AM, Hieu Hoang <hieuhoang@gmail.com
>> <mailto:hieuhoang@gmail.com>> wrote:
>>
>> Hi daniel
>>
>> On 15/11/14 22:02, Daniel Seita wrote:
>>> Hello everyone,
>>>
>>> I'm having some trouble installing boost, because it fails
>>> when running ./bjam -j8. I'm using Mac OS X 10.9.5. I have
>>> *g++* installed in:
>>>
>>> /usr/local/bin/g++-4.9
>> fyi, I think bjam will use the default c++ compiler on your
>> laptop, unless you tell it to. So it's actually using clang,
>> not g++, as you can see in the error message below
>>>
>>> and *boost* installed, via homebrew, in:
>>>
>>> ls /usr/local/Cellar/boost/1.56.0/
>>> INSTALL_RECEIPT.json include lib
>>>
>>> Notice that the above directory has the *include *and the
>>> *lib* directories, as required (according to bjam --help).
>>> Here is the command I ran:
>>>
>>> ./bjam --with-boost=/usr/local/Cellar/boost/1.56.0 -j8
>>>
>>> And I get a ton of errors that look the same, e.g.,
>>>
>>> darwin.link
>>> lm/bin/darwin-4.2.1/release/debug-symbols-on/link-static/threading-multi/query
>>> ld: warning: directory not found for option
>>> '-L/usr/local/Cellar/boost/1.56.0/lib64'
>>> ld: library not found for -lboost_thread
>>> clang: error: linker command failed with exit code 1 (use -v
>>> to see invocation)
>>>
>>> *It seems like the error is that the installer expects
>>> 'lib64' instead of 'lib'.* (Or could it be 'lib64' /and/
>>> 'lib'?) I did some searching but wasn't sure how to get the
>>> lib64 files. Does anyone have any idea? I have attached my
>>> build log.
>> the compiler looks in both lib and lib64 (if available) for
>> the library files. In your lib directory, is there a file called
>> libboost_thread.so
>> or
>> libboost_thread.a
>> ?
>> Personally, I would uninstall the boost library from homebrew
>> and compile my own boost library. Follow these instructions
>> if you want to do the same
>> http://www.statmt.org/moses/?n=Development.GetStarted
>>
>>>
>>> Thanks,
>>> Daniel
>>>
>>>
>>> _______________________________________________
>>> Moses-support mailing list
>>> Moses-support@mit.edu <mailto:Moses-support@mit.edu>
>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20141116/33e32c3a/attachment.htm

------------------------------

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 97, Issue 40
*********************************************

Tweet