#44398: kdelibs4 configure failure ---------------------------+--------------------- Reporter: ryandesign@… | Owner: nicos@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: Port: kdelibs4 | ---------------------------+--------------------- Comment (by nicos@…): 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. -- Ticket URL: <https://trac.macports.org/ticket/44398#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X