Stockfish 1.7.1 for Mac OS X

[Max]

Damned .. that was pretty easy

After the download from JA's site and unpacking, a simple "make osx-x86_64" did all the magic in a terminal.

./stockfish bench 128 1 14 default depth > bench.txt

gives this on my MacBook for 64 bit:

Code: Select all

===============================
Total time (ms) : 39207
Nodes searched  : 29196373
Nodes/second    : 744672

and after "make osx-x86" that for 32 bit:

Code: Select all

===============================
Total time (ms) : 60418
Nodes searched  : 29196373
Nodes/second    : 483239

Replacing the original sf171 with the new compile and voila .. the Stockfish gui starts smoothly!

Tord, thank you very much for this great gift to the mac community!

All the best,
Max

[Tord Romstad]

Damned .. that was pretty easy

I'm glad you managed to solve the problem, but I still don't think it is easy enough.

Having to compile the engine binary yourself, renaming it and moving it to the right location inside the application bundle is hardly a very user-friendly procedure. I need to find out why -isysroot/... and mmacosx-version=min=10.5 are not sufficient for me to compile a working Leopard binary.

It's tempting just to advice people to upgrade. Snow Leopard rocks, and it's a very cheap upgrade .

[IanO]

I need to find out why -isysroot/... and mmacosx-version=min=10.5 are not sufficient for me to compile a working Leopard binary.

The settings I needed to add when compiling a JNI library for 10.5 compatibility on a 10.6 system:

Code: Select all

export MACOSX_DEPLOYMENT_TARGET="10.5"
FLAGS = -isysroot /Developer/SDKs/MacOSX10.5.sdk -mmacosx-version-min=10.5 -arch x86_64
CFLAGS += $(FLAGS)
SOFLAGS += $(FLAGS)     # probably not needed for stockfish

The deployment target environment variable is key to retain the legacy dylib loading commands.

Ian

[sockmonkey]

Damned .. that was pretty easy

I'm glad you managed to solve the problem, but I still don't think it is easy enough.

Having to compile the engine binary yourself, renaming it and moving it to the right location inside the application bundle is hardly a very user-friendly procedure. I need to find out why -isysroot/... and mmacosx-version=min=10.5 are not sufficient for me to compile a working Leopard binary.

It's tempting just to advice people to upgrade. Snow Leopard rocks, and it's a very cheap upgrade .

If Ian's advice re: Deployment Target doesn't work, maybe check your GCC version. You might need to back down to 4.0 (we had to do this for our software, although it might have been a 10.4 or PPC compatibility thing, I simply don't remember).

Good luck!
Jeremy

[IanO]

P.S. On a different note, I hope the Icelandic ash cloud isn't causing Tord and his Norwegian friends too much inconvenience. I was just a kid when I helped my parents shovel ash off the roof from St. Helens. Best wishes, Ian