Hi, Patrick as your command "./bjam --with-giza=/project/tools/bin --with-irstlm=/project/tools/irstlm --with-srilm=/project/tools/srilm" and error information, I think that you set two Language Model,so you should check your configuration file moses.ini, such as the type of LM.
cheers, chen 2012/8/3 <moses-support-requ...@mit.edu> > 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-requ...@mit.edu > > You can reach the person managing the list at > moses-support-ow...@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. No moses executable (Patrick Bessler) > 2. Re: No moses executable (Daniel Schaut) > 3. Re: No moses executable (Patrick Bessler) > 4. Re: No moses executable (Pratyush Banerjee) > 5. Re: No moses executable (Patrick Bessler) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 02 Aug 2012 18:29:32 +0200 > From: Patrick Bessler <wil...@googlemail.com> > Subject: [Moses-support] No moses executable > To: moses-support@mit.edu > Message-ID: <501aaaec.8060...@googlemail.com> > Content-Type: text/plain; charset=ISO-8859-15; format=flowed > > Hi there, > > I am working with an Ubuntu 12.04 32bit machine. I have installed > GIZA++, IRSTLM and SRILM. Now, I cloned the mosesdecoder from github. > That went very well. I executed the bjam script and pointed to giza, > irst and sri. > bjam finished but I didn't have any dist or bin folder, there was also > no moses or moses chart executable. > > What kind of information can I additionally provide that you maybe could > help me. > > cheers, > Patrick > > > ------------------------------ > > Message: 2 > Date: Thu, 2 Aug 2012 18:46:15 +0200 > From: Daniel Schaut <danielsh...@hotmail.com> > Subject: Re: [Moses-support] No moses executable > To: "'Patrick Bessler'" <wil...@googlemail.com>, > <moses-support@mit.edu> > Message-ID: <snt104-ds10177460e9deb4777ca40fb1...@phx.gbl> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Patrick, > > I had the same problem about six months before: > http://www.mail-archive.com/moses-support@mit.edu/msg05119.html > > Unfortunately I can't remember how I fixed it, but the thread points to the > problem. Could you please provide your bjam command? > > Daniel > > -----Urspr?ngliche Nachricht----- > Von: moses-support-boun...@mit.edu [mailto:moses-support-boun...@mit.edu] > Im > Auftrag von Patrick Bessler > Gesendet: 02 August 2012 18:30 > An: moses-support@mit.edu > Betreff: [Moses-support] No moses executable > > Hi there, > > I am working with an Ubuntu 12.04 32bit machine. I have installed > GIZA++, IRSTLM and SRILM. Now, I cloned the mosesdecoder from github. > That went very well. I executed the bjam script and pointed to giza, irst > and sri. > bjam finished but I didn't have any dist or bin folder, there was also no > moses or moses chart executable. > > What kind of information can I additionally provide that you maybe could > help me. > > cheers, > Patrick > _______________________________________________ > Moses-support mailing list > Moses-support@mit.edu > http://mailman.mit.edu/mailman/listinfo/moses-support > > > > > ------------------------------ > > Message: 3 > Date: Thu, 02 Aug 2012 18:55:00 +0200 > From: Patrick Bessler <wil...@googlemail.com> > Subject: Re: [Moses-support] No moses executable > To: Daniel Schaut <danielsh...@hotmail.com> > Cc: moses-support@mit.edu > Message-ID: <501ab0e4.8000...@googlemail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Daniel, > > sure, here is the call (it is very close to the baseline tutorial) > "./bjam --with-giza=/project/tools/bin > --with-irstlm=/project/tools/irstlm --with-srilm=/project/tools/srilm" > I don't use the "j -X" option because I install Moses on a Virtual > Machine with 32bit. > > Patrick > > > Am 02.08.2012 18:46, schrieb Daniel Schaut: > > Hi Patrick, > > > > I had the same problem about six months before: > > http://www.mail-archive.com/moses-support@mit.edu/msg05119.html > > > > Unfortunately I can't remember how I fixed it, but the thread points to > the > > problem. Could you please provide your bjam command? > > > > Daniel > > > > -----Urspr?ngliche Nachricht----- > > Von: moses-support-boun...@mit.edu [mailto:moses-support-boun...@mit.edu] > Im > > Auftrag von Patrick Bessler > > Gesendet: 02 August 2012 18:30 > > An: moses-support@mit.edu > > Betreff: [Moses-support] No moses executable > > > > Hi there, > > > > I am working with an Ubuntu 12.04 32bit machine. I have installed > > GIZA++, IRSTLM and SRILM. Now, I cloned the mosesdecoder from github. > > That went very well. I executed the bjam script and pointed to giza, irst > > and sri. > > bjam finished but I didn't have any dist or bin folder, there was also no > > moses or moses chart executable. > > > > What kind of information can I additionally provide that you maybe could > > help me. > > > > cheers, > > Patrick > > _______________________________________________ > > Moses-support mailing list > > Moses-support@mit.edu > > http://mailman.mit.edu/mailman/listinfo/moses-support > > > > > > > > ------------------------------ > > Message: 4 > Date: Thu, 2 Aug 2012 18:48:32 +0100 > From: Pratyush Banerjee <pbaner...@computing.dcu.ie> > Subject: Re: [Moses-support] No moses executable > To: Patrick Bessler <wil...@googlemail.com> > Cc: moses-support@mit.edu > Message-ID: > < > cahu5gz7uxzcbbfu_ssmw1fck92h7edr8-xrqjq9gl80f+9b...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > HI Patrick, > > This may be a wild guess but are you sure that your system has the latest > boost libraries ? I had faced a sort of similar issue some time back and > that was because of the lack of boost libs in the system... > > Thanks and Regards, > > Pratyush > > On Thu, Aug 2, 2012 at 5:55 PM, Patrick Bessler <wil...@googlemail.com > >wrote: > > > Hi Daniel, > > > > sure, here is the call (it is very close to the baseline tutorial) > > "./bjam --with-giza=/project/tools/bin > > --with-irstlm=/project/tools/irstlm --with-srilm=/project/tools/srilm" > > I don't use the "j -X" option because I install Moses on a Virtual > > Machine with 32bit. > > > > Patrick > > > > > > Am 02.08.2012 18:46, schrieb Daniel Schaut: > > > Hi Patrick, > > > > > > I had the same problem about six months before: > > > http://www.mail-archive.com/moses-support@mit.edu/msg05119.html > > > > > > Unfortunately I can't remember how I fixed it, but the thread points to > > the > > > problem. Could you please provide your bjam command? > > > > > > Daniel > > > > > > -----Urspr?ngliche Nachricht----- > > > Von: moses-support-boun...@mit.edu [mailto: > moses-support-boun...@mit.edu] > > Im > > > Auftrag von Patrick Bessler > > > Gesendet: 02 August 2012 18:30 > > > An: moses-support@mit.edu > > > Betreff: [Moses-support] No moses executable > > > > > > Hi there, > > > > > > I am working with an Ubuntu 12.04 32bit machine. I have installed > > > GIZA++, IRSTLM and SRILM. Now, I cloned the mosesdecoder from github. > > > That went very well. I executed the bjam script and pointed to giza, > irst > > > and sri. > > > bjam finished but I didn't have any dist or bin folder, there was also > no > > > moses or moses chart executable. > > > > > > What kind of information can I additionally provide that you maybe > could > > > help me. > > > > > > cheers, > > > Patrick > > > _______________________________________________ > > > Moses-support mailing list > > > Moses-support@mit.edu > > > http://mailman.mit.edu/mailman/listinfo/moses-support > > > > > > > > > > _______________________________________________ > > Moses-support mailing list > > 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/20120802/7342ae43/attachment-0001.htm > > ------------------------------ > > Message: 5 > Date: Thu, 02 Aug 2012 20:32:39 +0200 > From: Patrick Bessler <wil...@googlemail.com> > Subject: Re: [Moses-support] No moses executable > To: Kenneth Heafield <mo...@kheafield.com>, moses-support@mit.edu, > pbaner...@computing.dcu.ie > Message-ID: <501ac7c7.6030...@googlemail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Kenneth, > > I did rerun the bjam and attached you'll get the stdout.txt. The stderr > was empty. > > @Pratyush: yes. I setup the Ubuntu just yesterday and I installed the > latest libboost-all-dev. > > Best, > Patrick > > Am 02.08.2012 18:55, schrieb Kenneth Heafield: > > Hi, > > > > bjam may have finished, but did it actually terminate without > > errors? A quick test is to run bjam again. It will retry everything > > that failed the first time. Please rerun, attaching your stdout and > > stderr. > > > > Kenneth > > > > On 08/02/2012 12:29 PM, Patrick Bessler wrote: > >> Hi there, > >> > >> I am working with an Ubuntu 12.04 32bit machine. I have installed > >> GIZA++, IRSTLM and SRILM. Now, I cloned the mosesdecoder from github. > >> That went very well. I executed the bjam script and pointed to giza, > >> irst and sri. > >> bjam finished but I didn't have any dist or bin folder, there was also > >> no moses or moses chart executable. > >> > >> What kind of information can I additionally provide that you maybe could > >> help me. > >> > >> cheers, > >> Patrick > >> _______________________________________________ > >> Moses-support mailing list > >> Moses-support@mit.edu > >> http://mailman.mit.edu/mailman/listinfo/moses-support > > > > -------------- next part -------------- > warning: No toolsets are configured. > warning: Configuring default toolset "gcc". > warning: If the default is wrong, your build may not work correctly. > warning: Use the "toolset=xxxxx" option to override our guess. > warning: For more configuration options, please consult > warning: > http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!! You are linking the IRSTLM library; be sure the release is >= 5.70.02 > !!! > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > ...patience... > ...found 2630 targets... > ...updating 26 targets... > gcc.compile.c++ > moses/src/LM/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/Factory.o > gcc.archive > moses/src/LM/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/libLM.a > gcc.compile.c++ > moses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/StaticData.o > moses/src/StaticData.cpp: In Elementfunktion ?void > Moses::StaticData::SetExecPath(const string&)?: > moses/src/StaticData.cpp:1358:39: Fehler: ?class boost::filesystem3::path? > hat kein Element namens ?native_file_string? > > "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall > -g -pthread -DNDEBUG -DTRACE_ENABLE=1 -DWITH_THREADS > -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I"." -I"moses/src" -c -o > "moses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/StaticData.o" > "moses/src/StaticData.cpp" > > ...failed gcc.compile.c++ > moses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/StaticData.o... > ...skipped > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a(clean) > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>StaticData.o... > ...skipped > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>StaticData.o... > ...skipped > <pmoses-chart-cmd/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>moses_chart > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped > <pmoses-cmd/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>moses > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped > <pmoses-cmd/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>lmbrgrid > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped > <pOnDiskPt/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>CreateOnDiskPt > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped > <pOnDiskPt/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>queryOnDiskPt > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped > <pmisc/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>processPhraseTable > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped > <pmisc/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>processLexicalTable > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped > <pmisc/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>queryPhraseTable > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped > <pmisc/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>queryLexicalTable > for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/bin>moses_chart for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/bin>moses for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/bin>lmbrgrid for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/bin>CreateOnDiskPt for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/bin>queryOnDiskPt for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/bin>processPhraseTable for lack > of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/bin>processLexicalTable for lack > of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/bin>queryPhraseTable for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/bin>queryLexicalTable for lack of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > ...skipped <p/project/tools/mosesdecoder/lib>libmoses_internal.a for lack > of > <pmoses/src/bin/gcc-4.6/release/debug-symbols-on/link-static/threading-multi>libmoses_internal.a... > common.copy /project/tools/mosesdecoder/lib/libLM.a > ...failed updating 1 target... > ...skipped 21 targets... > ...updated 4 targets... > > ------------------------------ > > _______________________________________________ > Moses-support mailing list > Moses-support@mit.edu > http://mailman.mit.edu/mailman/listinfo/moses-support > > > End of Moses-support Digest, Vol 70, Issue 9 > ******************************************** >
_______________________________________________ Moses-support mailing list Moses-support@mit.edu http://mailman.mit.edu/mailman/listinfo/moses-support