i think that's the bjam that's installed by yum, rpm or whatever. Because moses won't compile when I type bjam It must be ./bjam
On Wed, Jan 18, 2012 at 9:54 PM, Kenneth Heafield <[email protected]>wrote: > The problem is this old website: http://www.boost.org/boost-build2/ . > The "Download" link yields a version from September 2007. This appears > to be what you have installed. Since September 2007, bjam is > distributed with the Boost tarball. The version distributed with Boost > is what the Jamfiles are based on and what I have copied into Moses. > > Kenneth > > On 01/18/2012 05:34 AM, Stefan Dumitrescu wrote: > > Hello, > > > > Well, i can't believe i forgot to add the dot/slash. It's because > > yesterday i had another problem on the same machine, the builder said it > > could not find boost.build even though everything was apparently ok. > > This morning out of desperation i rebooted the server (which was up for > > the last 4 months), and the error magically went away. I retyped the > > command and then it failed with the error below (i missed the ./ this > > time..). Then, i said: @moses-support time :) > > > > sdumitrescu /usr/local/trans/tools/moses > uname -a > > Linux helios 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:17:25 UTC > > 2011 x86_64 x86_64 x86_64 GNU/Linux > > > > sdumitrescu /usr/local/trans/tools/moses > lsb_release -a > > No LSB modules are available. > > Distributor ID: Ubuntu > > Description: Ubuntu 11.04 > > Release: 11.04 > > Codename: natty > > > > sdumitrescu /usr/local/trans/tools/moses > bjam --version > > Boost.Build V2 (Milestone 12) > > Boost.Jam 03.1.16 > > > > Moses compiled ok, thankfully. > > > > Thanks, > > Stefan > > //The server is 11.04 not 10.10 as i previously stated. > > > > On 1/18/2012 12:18 PM, Barry Haddow wrote: > >> On Wednesday 18 January 2012 10:07:59 Hieu Hoang wrote: > >>> i think it's > >>> ./bjam > >>> rather than > >>> bjam > >> Actually both should work. The former compiles and runs a version of > bjam > >> distributed with moses, whereas the latter runs an installed version of > bjam > >> (if there is one). > >> > >> The error that Stefan reported is rather odd as it appears that his > version of > >> bjam has a different signature for the option.get operation. > >> > >> My version is this: > >> [tyr]bhaddow: bjam --version > >> Boost.Build V2 (Milestone 12) > >> Boost.Jam 03.1.18 > >> > >> and /usr/share/boost-build/util/option.jam shows me that the signature > is > >> > >> rule get ( name : default-value ? : implied-value ? ) > >> > >> which is compatible with the Moses Jamfile. > >> > >> What's does your version of option.jam look like, Stefan? > >> > >> cheers - Barry > >> > >> > >>> perhaps we should rename it > >>> ./run-bjam > >>> to avoid confusion > >>> > >>> On Wed, Jan 18, 2012 at 4:58 PM, Stefan Dumitrescu< > >>> > >>> [email protected]> wrote: > >>>> Hello! > >>>> > >>>> Me again, this time with on a different server and with a different > moses > >>>> bjam build issue. > >>>> > >>>> I partially hijacked this thread because it seems to be somewhat > related. > >>>> > >>>> So, building moses on a ubuntu 64 10.10 server (after building mgiza > and > >>>> srilm without problems), i run: > >>>> > >>>> sdumitrescu /usr/local/trans/tools/moses> bjam > >>>> --with-srilm=/usr/local/trans/tools/srilm > >>>> --with-giza=/usr/local/trans/tools/mgiza/bin > >>>> > >>>> Jamroot:73: in modules.load > >>>> *** argument error > >>>> * rule option.get ( name : default-value ? ) > >>>> * called with: ( clean : : yes ) > >>>> * extra argument yes > >>>> /usr/share/boost-build/util/option.jam:11:see definition of rule 'get' > >>>> being called > >>>> /usr/share/boost-build/build/project.jam:312: in load-jamfile > >>>> /usr/share/boost-build/build/project.jam:68: in load > >>>> /usr/share/boost-build/build/project.jam:170: in project.find > >>>> /usr/share/boost-build/build-system.jam:248: in load > >>>> /usr/share/boost-build/kernel/modules.jam:261: in import > >>>> /usr/share/boost-build/kernel/bootstrap.jam:132: in boost-build > >>>> /usr/share/boost-build/boost-build.jam:1: in module scope > >>>> > >>>> I suspect it is boost-related, but after searching for solutions > without > >>>> any success, i come to you for advice :) > >>>> > >>>> Boost seems to be ok, it was installed by default with the server. > Tried > >>>> to reinstall: > >>>> sdumitrescu /usr/local/trans/tools/moses> sudo apt-get install > >>>> --reinstall libboost-all-dev > >>>> [sudo] password for sdumitrescu: > >>>> Reading package lists... Done > >>>> Building dependency tree > >>>> Reading state information... Done > >>>> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not > >>>> upgraded. > >>>> Need to get 0 B/1,498 B of archives. > >>>> After this operation, 0 B of additional disk space will be used. > >>>> (Reading database ... 113706 files and directories currently > installed.) > >>>> Preparing to replace libboost-all-dev 1.42.0.1ubuntu1 (using > >>>> .../libboost-all-dev_1.42.0.1ubuntu1_amd64.deb) ... > >>>> Unpacking replacement libboost-all-dev ... > >>>> Setting up libboost-all-dev (1.42.0.1ubuntu1) ... > >>>> > >>>> Same for boost-build: > >>>> sdumitrescu /usr/local/trans/tools/moses> sudo apt-get install > >>>> --reinstall boost-build > >>>> Reading package lists... Done > >>>> Building dependency tree > >>>> Reading state information... Done > >>>> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not > >>>> upgraded. > >>>> Need to get 0 B/365 kB of archives. > >>>> After this operation, 0 B of additional disk space will be used. > >>>> (Reading database ... 113706 files and directories currently > installed.) > >>>> Preparing to replace boost-build 2.0-m12-2 (using > >>>> .../boost-build_2.0-m12-2_all.deb) ... > >>>> Unpacking replacement boost-build ... > >>>> Setting up boost-build (2.0-m12-2) ... > >>>> > >>>> > >>>> Thanks for your suggestions, > >>>> Stefan > >>>> > >>>> > >>>> > >>>> On 1/12/2012 7:42 AM, Hieu Hoang wrote: > >>>> > >>>> You have to move boost into the correct directories for gcc to see > it. I > >>>> personally install boost using macports which takes care of those > things > >>>> > >>>> On Thursday, January 12, 2012, Hobli Taffame<[email protected]> > wrote: > >>>>> Hi, > >>>>> I am trying to setup moses on Mac OS X 10.7.2 using the using the > steps > >>>> from: http://www.statmt.org/moses_steps.html#versions > >>>> > >>>>> The steps I have successfully configured are: > >>>>> > >>>>> download and compile GIZA++ and mkcls > >>>>> download and compile SRILM > >>>>> download and compile IRSTLM > >>>>> download and compile boost > >>>>> clone moses > >>>>> > >>>>> But when I try to compile it: > >>>>> ./jam --with-srilm=/path/to/this/directory > >>>> --with-irstlm=/path/to/this/directory --with-giza=/path/to/the/bin -j2 > >>>> > >>>>> I just get the following error: > >>>>> -> Boost does not seem to be installed or g++ is confused. > >>>>> Please can you help me to fix this? > >>>>> Best regards > >>>>> Thayd > >>>> _______________________________________________ > >>>> Moses-support mailing > >>>> [email protected]:// > mailman.mit.edu/mailman/listinfo/moses-su > >>>> pport > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Moses-support mailing list > >>>> [email protected] > >>>> http://mailman.mit.edu/mailman/listinfo/moses-support > >> > >> -- > >> Barry Haddow > >> University of Edinburgh > >> +44 (0) 131 651 3173 > >> > > > > _______________________________________________ > > Moses-support mailing list > > [email protected] > > http://mailman.mit.edu/mailman/listinfo/moses-support > _______________________________________________ > Moses-support mailing list > [email protected] > http://mailman.mit.edu/mailman/listinfo/moses-support >
_______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
