Created attachment 111411 [details] CMake error log When trying to build Falkon 3.0.0, I get a linking error. ``` [ 52%] Linking CXX shared library ../../bin/libFalkonPrivate.so /usr/lib/libQt5Network.so.5.9.3: warning: warning: EVP_CipherFinal is often misused, please use EVP_CipherFinal_ex and EVP_CIPHER_CTX_cleanup collect2: error: ld returned 1 exit status ``` Viewing CMakeError.log it seems it's a detection of glibc gone wrong. Note that this system uses musl rather than glibc. ``` /home/pmos/build/src/falkon-3.0.0/CMakeFiles/CMakeTmp/CheckSymbolExists.c: In function 'main': /home/pmos/build/src/falkon-3.0.0/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:19: error: '__GLIBC__' undeclared (first use in this function) return ((int*)(&__GLIBC__))[argc]; ^~~~~~~~~ ```
Please post full output, or at least last 200 lines.
Created attachment 111412 [details] CMake output log Note that CMake reports the system is Gentoo, this only is for the kernel. I'm actually building this in a Alpine Linux chroot.
I meant output you see in terminal, not what CMake saves in log files. But it fails due to LibreSSL, probably because EVP_CipherFinal is not defined? It will be evident from linker output.
Created attachment 111413 [details] CMake terminal output Ah sorry, my mistake. I find the terminal output quite useless really, it has no indication why it failed. But here it is.
Yes, it's LibreSSL incompatibility in this case. You should use OpenSSL instead.
That won't be as easy sadly. It would mean I'd have to replace LibreSSL for OpenSSL in the *entire* dependency chain, including all of Qt5. And that's not up to me to decide :(
Then there is also possibility that Qt was built using OpenSSL and you are trying to build Falkon with LibreSSL, or the other way around. The linking error comes from libQt5Network.so.5.9.3, not Falkon.
Actually this is just linker warning, and linker warnings are treated as errors by default in KF5. You can workaround it by changing linker flags to disable treating warnings as errors.
We switched to OpenSSL, so this bug is not relevant anymore.