Sylvain Gelly: <[EMAIL PROTECTED]>: >> >> tried to open opening, success 0 <-- in grey >> >Here it does not find the file, because the file is with the binaries >> >and gogui (at least your version) looks into the gogui/bin directory. >> >But that does not prevent MoGo to work. >> >> I guess so, as when I added "--useOpeningDatabase 0" it's almost the >> same except the message. > >As I read my sentence, it was not clear :). I meant "because the >opening file is in the same directory as the mogo binary"
Hmmm, it may be wrong. The files, opening and openingValues_19, are surely in the same directory as the mogo binary. When I invoke mogo at the directory where the opening files are, the message changes to "Load opening database opening succeed (nbEntries=618) (nbIllegal moves removed 0) tried to open opening, success 1". I guess the search path you've coded is something wrong or different depends on the distributions. I'd like to suggest to use some environment variable dedicated to mogo. >> MoGo works fine with command line. Say, >> genmove b >> = E5 >> genmove w >> = G6 >> with lots of trace messages and the board in ascii. > >Ok, so obviously it is something in the communication with gogui, that >is so strange, especially that it does not happen for me... I think it's not so strange. It's just depending on the distribution or dynamic libraries mogo uses, I guess. Are you flushing stdout and stderr explicitly with or without lock? If so, when and from what thread? -gg -- [EMAIL PROTECTED] (Kato) _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
