Try git pull. $(which bjam) should run bjam because it expands to the path of bjam. echo $(which bjam) should print the path to the executable.
I suspect you have an odd version of which that returns success even if it doesn't find anything and an empty argument to grep was causing it to expect stdin. Kenneth "of which that" Heafield On 12/13/11 07:53, John Morgan wrote: > I think this is my problem: > The command substitution $(which bjam) in my environment is not doing > what you intended it to do. > In my environment it's running bjam. > I invoke ./bjam from an emacs shell buffer. Could this be the cause of > the problem? > John > > > On 12/12/11, Kenneth Heafield <[email protected]> wrote: >> Hi, >> >> ./bjam is supposed to either delegate to your system bjam (if >> satisfactory) or compile bjam (if it hasn't already) then delegate to >> it. That's how it works for me and I've tested this on machines with >> and without bjam installed. >> >> ./bjam is a simple shell script and I'm not sure why it would echo >> nothing to the terminal (unless it's satisfied that everything is >> built). Also try: >> >> rm jam-files/bjam >> >> Otherwise, hopefully you can look at the shell script and fix it >> because everything looks fine from my end. You do have bash installed, >> right? >> >> Kenneth >> >> On 12/12/11 15:24, John Morgan wrote: >>> Kenneth, >>> I have bjam on my path. When I invoke ./bjam in the mosesdecoder >>> directory, nothing happens, at least nothing is echoed to the >>> terminal. Everything runs fine when I run just "bjam" without the dot >>> slash. >>> Is this what I should expect? >>> >> _______________________________________________ >> 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
