dbusmenu-qt5 build failure on 10.7 and 10.8 buildbots because of using libstdc++

Mojca Miklavec mojca at macports.org
Thu Oct 6 06:33:20 PDT 2016

On 6 October 2016 at 15:08, Ryan Schmidt wrote:
> Let's take the qt5-qtbase port as an example. It depends on the icu port. Its library /opt/local/libexec/qt5/lib/QtCore.framework/QtCore links with icu's libraries /opt/local/lib/libicui18n.55.dylib, /opt/local/lib/libicuuc.55.dylib, /opt/local/lib/libicudata.55.dylib, and also (on my El Capitan system) /usr/lib/libc++.1.dylib. If we force qt5-qtbase to use libc++, it will link with libc++ even on vanilla OS X 10.7 and 10.8 systems.
> Icu's /opt/local/lib/libicui18n.55.dylib and /opt/local/lib/libicuuc.55.dylib libraries also link (on my El Capitan system) with /usr/lib/libc++.1.dylib. On vanilla 10.7 and 10.8, it would link with libstdc++ instead.
> Does QtCore pass C++ objects to libicui18n or libicuuc? I don't know. If it does, that won't work if the C++ libraries are mismatched.

I must have confused something, sorry. Apparently only qt5-qtwebkit
includes PortGroup cxx11 1.0. I thought that the whole of Qt5 required
C++11, but I was wrong.

Some of the old posts (that probably kept me confused):
- https://lists.macosforge.org/pipermail/macports-dev/2015-December/031986.html
- https://lists.macosforge.org/pipermail/macports-dev/2015-December/031999.html
- https://lists.macosforge.org/pipermail/macports-dev/2015-December/031992.html


More information about the macports-dev mailing list