multiple problems with mysql + pkg'ized ssl lib

[anttikantee]

1. mysql does not accept version "2" of libressl
   => either teach it to accept that, or package openssl and use that if you want mysql
2. cmake does not find pkgs dir outside of CMAKE_FIND_ROOT_PATH
   => either put pkgs dir under root, or otherwise play games with cmake

[Ulrar]

Not quite sure what to do with this. I've tried exporting CMAKE_FIND_ROOT_PATH to where I cloned rumrun-packages/pkgs but that doesn't work, or are you not referencing an env variable ?

[kaveman-]

tried passing -DCMAKE_FIND_ROOT_PATH to cmake?

[Ulrar]

Just tried, the final command run is :

cd /home/username/workspace/rumprun-packages/mysql/build/mysql/build-cross && cmake \
    -C /home/username/workspace/rumprun-packages/mysql/CachePreseed.cmake \
    -DCMAKE_TOOLCHAIN_FILE=/home/username/workspace/rumprun/./rumprun/rumprun-x86_64/share/x86_64-rumprun-netbsd-toolchain.cmake \
    -DSTACK_DIRECTION=-1 \
    -DDISABLE_SHARED=ON \
    -DWITH_ZLIB=system \
    -DWITH_SSL=system \
    -DFEATURE_SET=small \
    -DWITHOUT_PERFSCHEMA_STORAGE_ENGINE=1 \
		-DCMAKE_FIND_ROOT_PATH=/home/username/workspace/rumprun-packages/pkgs \
    ..

Still the same error. Whatever the actual solution is, might be a good idea to add a note in the README, I can't be the only one who doesn't know how cmake works.

[Ulrar]

Allright, figured it out.
I ran make in the openssl directory myself, then I added

SET(CMAKE_FIND_ROOT_PATH "/home/username/workspace/rumprun-packages/pkgs")

On line 419 of build/mysql/CMakeLists.txt, that solved the openssl detection problem.

Then I had to add

SET(HAVE_SHA512_DIGEST_LENGTH TRUE)

on line 221 of build/mysql/cmake/ssl.cmake, just before the if. It should have been true already, I checked by hand, but for some reason it wasn't .. That might just be my cmake version I suppose.

In any case, could be a good idea to add a note in the README to say where to add the SET in the CMakeLists.txt

[anttikantee]

Nice.

Can that be automatically patched as part of the build process?

btw, you might want to update the openssl package to the latest, probably not more complicated than bumping the version number.