https://bugs.kde.org/show_bug.cgi?id=436958
--- Comment #16 from michael <reeves...@gmail.com> --- The offending Qt lines are here: #if !defined(Q_ASSERT) # if defined(QT_NO_DEBUG) && !defined(QT_FORCE_ASSERTS) # define Q_ASSERT(cond) static_cast<void>(false && (cond)) # else # define Q_ASSERT(cond) ((cond) ? static_cast<void>(0) : qt_assert(#cond, __FILE__, __LINE__)) # endif #endif The expression static_cast<void>(false && (cond)) is produced when qt thinks this Q_ASSERT should be disabled. Since it seems to be problematic on some configurations Q_ASSERT should not be used for anything that has side effects. I will push a fix shortly to replace Q_ASSERT with assert in the connection macros. This will prevent the issue from reoccurring. Build with an explicit CMAKE_BUILD_TYPE=Debug should workaround it until the hot fix 1.9.1 release because available later today or tomorrow. This bug will be closed when the patch is pushed to git. -- You are receiving this mail because: You are watching all bug changes.
