compile error

[rwst]

This is with gcc-4.8.3

ralf@ark:~/Gull/src> make
clang++ -msse4.1 -mpopcnt -fpermissive -fno-exceptions -fno-rtti -w -O2 Gull.cpp -o Gull
Gull.cpp:416:1: error: C++ requires a type specifier for all declarations
__declspec(align(64)) GBoard Board[1];
^
Gull.cpp:416:12: error: use of undeclared identifier 'align'
__declspec(align(64)) GBoard Board[1];
           ^
Gull.cpp:416:22: error: expected ';' after top level declarator
__declspec(align(64)) GBoard Board[1];                                                  
                     ^                                                                  
                     ;                                                                  
Gull.cpp:439:1: error: C++ requires a type specifier for all declarations               
__declspec(align(64)) GData Data[128];                                                  
^                                                                                       
Gull.cpp:439:12: error: use of undeclared identifier 'align'
__declspec(align(64)) GData Data[128];
           ^
Gull.cpp:439:22: error: expected ';' after top level declarator
__declspec(align(64)) GData Data[128];
                     ^
                     ;
Gull.cpp:481:1: error: C++ requires a type specifier for all declarations
__declspec(align(64)) GPawnEntry PawnHash[pawn_hash_size];
^
Gull.cpp:481:12: error: use of undeclared identifier 'align'
__declspec(align(64)) GPawnEntry PawnHash[pawn_hash_size];
           ^
Gull.cpp:481:22: error: expected ';' after top level declarator
__declspec(align(64)) GPawnEntry PawnHash[pawn_hash_size];

[rwst]

ah I just see you call clang---my clang is 3.7.0

[basil00]

My clang is older, version 3.5. Maybe try that until a solution is found?

[basil00]

Should be fixed now?

[rwst]

Sorry, yes, thanks. I had to also set sse to 3 because I'm on AMD but then
it compiled fine and played two games against SF.

On Wed, 21 Oct 2015 15:23 basil00 notifications@github.com wrote:

Should be fixed now?

—
Reply to this email directly or view it on GitHub
#1 (comment).