64bit compile of MariaDB 10.0.21 for Solaris 10 (sparc)

I'm having a really rough time with this. Both using the BUILD/compile_solaris_spac, cmake . -DBUILD_CONFIG=mysql_release and just going through regular config script. Compiling in 32bit wasn't an issue, but I need a 64bit installation.

I've set all of my flags to inclued -m64:

  1. env | grep FLAGS CPPFLAGS=-m64 CMAKE_C_FLAGS=-m64 CXXFLAGS=-m64 CMAKE_CXX_FLAGS=-m64 CFLAGS=-m64

And my library path is correct - as far as I can tell.

  1. echo $LD_LIBRARY_PATH /usr/lib/sparcv9:/usr/sfw/lib/sparcv9:/lib/sparcv9:/lib:/usr/lib

So far I've had to manually change all of the link.txt files to add the -m64 switch. That got me past the initial problem, but now I'm running into the following:

[ 18%] Building C object mysys/CMakeFiles/mysys.dir/my_atomic.c.o cd /opt/install/mariadb-10.0.21/mysys && /usr/sfw/bin/gcc -DHAVE_CONFIG_H -DHAVE_RWLOCK_T -m64 -O3 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized -DDBUG_OFF -I/opt/install/mariadb-10.0.21/include -I/opt/install/mariadb-10.0.21/mysys -m64 -fPIC -o CMakeFiles/mysys.dir/my_atomic.c.o -c /opt/install/mariadb-10.0.21/mysys/my_atomic.c /opt/install/mariadb-10.0.21/mysys/my_atomic.c: In function `my_atomic_initialize': /opt/install/mariadb-10.0.21/mysys/my_atomic.c:30: error: size of array `compile_time_assert' is negative * Error code 1 make: Fatal error: Command failed for target `mysys/CMakeFiles/mysys.dir/my_atomic.c.o' Current working directory /opt/install/mariadb-10.0.21 * Error code 1 make: Fatal error: Command failed for target `mysys/CMakeFiles/mysys.dir/all' Current working directory /opt/install/mariadb-10.0.21 * Error code 1 make: Fatal error: Command failed for target `all'

Any and all help would be greatly appreciated.

Answer Answered by Vladislav Vaintroub in this comment.

this looks like a bug in connect engine, though I do not really understand the error message. you can file a bug , and temporarily disable connect storage engine by doing

cmake .. -DWITH_CONNECT_STORAGE_ENGINE=0

in the build directory.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.