Fixed. FWIW, to the extent that it exists, the low-level language is documented at http://www.boost.org/boost-build2/doc/html/jam/language.html .
Kenneth On 04/02/2012 01:46 PM, Lane Schwartz wrote: > On Fri, Mar 30, 2012 at 8:01 PM, Kenneth Heafield <[email protected] > <mailto:[email protected]>> wrote: > > Dear Moses, > > By popular demand (Lane e-mailed me), when you run bjam, it > will save the arguments into previous.sh in the top-level Moses > directory. Then you can run ./previous.sh and it will use the > remembered arguments. One caveat: it doesn't know how to do shell > escaping, so people with spaces and other weird characters in their > paths beware. > > Kenneth > > > Ken, > > The new previous.sh isn't working for me. Steps to reproduce are below: > > $ ./bjam --with-synlm > > * wait for things to correctly build * > > $ ./previous.sh > > * dies with error message * > > Unable to load Boost.Build: could not find "boost-build.jam" > ----------------------------------------------------- > Attempted search from /path/to/mosesdecoder up to the root at > /path/to/mosesdecoder/share/boost-build. and in these directories from > BOOST_BUILD_PATH and BOOST_ROOT: /usr/share/boost-build > > > $ cat ./previous.sh > > #!/bin/bash > ./jam-files/bjam --with-synlm > > > > If I rerun my original command "./bjam --with-synlm" that works fine. > > I assume the problem is that previous.sh is prefixing the call to bjam > with "./jam-files" but I don't know enough about Jamroot to fix the > problem in the code there. > > Thanks, > Lane > _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
