Current mariadb ebuilds (tested with 10.1.18 and 10.1.19) cause the lz4/lzo/snappy support to never be built. Commenting out following definitions in ebuild causes the autodetection to kick in and support is built in just fine. MYSQL_CMAKE_NATIVE_DEFINES+=( ... #-DWITH_INNODB_LZ4=$(usex innodb-lz4) #-DWITH_INNODB_LZO=$(usex innodb-lzo) #-DWITH_INNODB_SNAPPY=$(usex innodb-snappy) I've tested this with cmake 3.3 and 3.5 with the same result.
Please attach a full build.log demonstrating the issue
Created attachment 453048 [details] Build log of original ebuild
Created attachment 453064 [details] Build log of commented out ebuild
I have attached two xzipped build.logs. One demonstrates the original behavior and the other one behavior after commenting out three aforementioned lines. Hope it helps.
Ok.. Now i see the issue. "-DWITH_INNODB_LZ4=yes -DWITH_INNODB_LZO=yes -DWITH_INNODB_SNAPPY=yes" is incorrect. The ebuild should be fixed to be: MYSQL_CMAKE_NATIVE_DEFINES+=( ... -DWITH_INNODB_LZ4=$(usex innodb-lz4 ON OFF) -DWITH_INNODB_LZO=$(usex innodb-lzo ON OFF) -DWITH_INNODB_SNAPPY=$(usex innodb-snappy ON OFF) Auto-detection is not acceptable as the dependencies can be off wildly.
Oh, don't get me wrong. I was not suggesting autodetection as a solution. It was a mere work-around for me. Sorry if that wasn't clear. btw. I was looking at the ebuild and just got curious if it's the case with the rest of the plain usex flags. I'll test it and let you know.
Fixed with mariadb-10.1.19-r1
