kdelibs4 configure failure

[ryandesign (Ryan Carsten Schmidt)]

kdelibs4 @4.12.5_3 is failing to configure for me. kdelibs4 @4.12.5_1 is currently installed. I'm actually having trouble reading the log and figuring out what the problem is. I do see:

-- Performing Test HAVE_QSSLSOCKET
-- Performing Test HAVE_QSSLSOCKET - Failed
CMake Error at kdecore/network/ConfigureChecks.cmake:22 (message):
  KDE Requires Qt to be built with SSL support
Call Stack (most recent call first):
  kdecore/CMakeLists.txt:23 (include)

However, qt4-mac is of course installed with ssl support (there is no option not to do that).

[NicosPavlov]

I cannot reproduce the issue, but for reference, kdecore/CMakeLists.txt at line 23 is:

include(network/ConfigureChecks.cmake)

and the file ConfigureChecks.cmake contains the test:

macro_push_required_vars()
  set(CMAKE_REQUIRED_INCLUDES "${CMAKE_REQUIRED_INCLUDES};${QT_INCLUDE_DIR}")
  if (QT_USE_FRAMEWORKS)
    set(CMAKE_REQUIRED_FLAGS "-F${QT_LIBRARY_DIR} ")
  endif (QT_USE_FRAMEWORKS)
  check_cxx_source_compiles(
"#include <QtNetwork/QSslSocket>
int main()
{
    QSslSocket *socket;
    return 0;
}" HAVE_QSSLSOCKET)
  if (NOT HAVE_QSSLSOCKET)
    message(SEND_ERROR "KDE Requires Qt to be built with SSL support")
  endif (NOT HAVE_QSSLSOCKET)
macro_pop_required_vars()

which means that it is again a case where cmake tries to compile some code, fails for any reason, and gives the issue at the place of the code, which is not necessarily linked to ssl here. It seems very similar to #41321, where there were issues with how cmake was configured. I strongly suspect that the recent changes to the cmake portgroup, which reverted some of the changes related to #41321, induced a regression (see in particular r122298 and r122339, linked to #44125).

I suspect that even kdelibs4@4.12.5_1 would also fail the configure stage, but by reverting the cmake portgroup and cmake to 3.0.0_2, the error of this ticket would not happen.

[ryandesign (Ryan Carsten Schmidt)]

I've been having problems building kdelibs4 for over a week already, but only reported it now. But I don't know if the error I got earlier was the same or different.

[NicosPavlov]

I see. I saw two differences between your log and my system. The first one is that you have
'-DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk"',
while mine is
-DCMAKE_OSX_SYSROOT="/"
which is probably as you have configure.sdkroot set, but this should not be the issue, as setting the sdk was not causing configure errors previously.

The other one is universal build, that I could not test yet, because of other ports issues to rebuild the set.

Nevertheless, the log shows that there is an issue with cmake trying to build anything, as all tests based on compilation tests, such as

:info:configure -- Performing Test HAVE_X86_SSE
:info:configure -- Performing Test HAVE_X86_SSE - Failed

which is based on

check_cxx_source_compiles("int main() { __asm { xorps xmm0, xmm0 }; }" HAVE_X86_SSE)

The error announced about ssl is just the one picked up within many others, even though I do not know what is causing this.

[mkae (Marko Käning)]

Cc Me!

[mkae (Marko Käning)]

Is this still an issue?

[chrstphrchvz (Christopher Chavez)]

No activity on this ticket in over 4 years, should this be closed?