acepoint wrote:Babelardus wrote:
If it's dynamically linked, it won't run on Macs on which the Boost libraries are not installed, unless you provide them along with the program.
I know. That's why I mentioned it. But various flags produced errors. I tried:
./configure LDFLAGS="-static"
or
./configure --enable-static
or
make SHARED=0 CC='gcc -static' CXX='g++ -static'
etc
This is correct; I also can't statically link the C++ runtime libraries on Windows.
Fuego r2029 seemingly has some bugs. It plays 'nicer' Go than version 1.1, due to its new patterns, but I don't know yet if it's really stronger than the old version, because it's so slow. Versio 1.1. runs at a speed of about 16.000 playouts per second on my machine, while the new version that I've compiled runs at 600 games/seconds. That's almost 27 times slower. I've been able to recompile and optimize it to run at 800 games/second, but stil...
I've tried compiling with -O2, -O3, compiled against Boost 1.61, 1.51, and several versions in between, also tried compiling Boost with different optimizations (and obviously, everything as 'release'), but r2029 stays extremely slow compared to the older 1.1.
For the old 1.1 version I didn't do anything special with regard to optimizations. I just compiled Boost 1.49 and Fuego 1.1 with -03 and all options enabled for SSE3 CPU's.
That version has it's own problems though. Because Boost 1.49 is the last version to provide the Filesystem v2 library, and the first version that compiles under GCC 4.6 and newer, it's (almost) impossible to get Fuego 1.1 to compile with anything else but Boost 1.49 under a new compiler, and that *still* requires hacking both Boost's build scripts and Fuego's code.