#42710: digikam 3.5 not compiling with jpeg @9a_0 ------------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: fixed | Keywords: Port: digikam | ------------------------+-------------------------------- Comment (by jul_bsd@…): compile/install well for me. execution still fails but probably another story... {{{ $ /path/to/digikam [...] objc[11708]: Class QNSStatusItem is implemented in both /opt/local/Library/Frameworks/QtGui.framework/Versions/4/QtGui_debug and /opt/local/Library/Frameworks/QtGui.framework/Versions/4/QtGui. One of the two will be used. Which one is undefined. [...] dyld: loaded: /opt/local/lib/kde4/plugins/imageformats/kimg_rgb.so dyld: loaded: /opt/local/lib/kde4/plugins/imageformats/kimg_tga.so dyld: loaded: /opt/local/lib/kde4/plugins/imageformats/kimg_webp.so dyld: loaded: /opt/local/lib/libwebp.5.dylib QObject::moveToThread: Current thread (0x7fdba8400bb0) is not the object's thread (0x7fdba877b770). Cannot move to target thread (0x7fdba8400bb0) On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded. dyld: loaded: /opt/local/lib/kde4/plugins/imageformats/kimg_xcf.so dyld: loaded: /opt/local/lib/kde4/plugins/imageformats/kimg_xview.so dyld: loaded: /opt/local/share/qt4/plugins/imageformats/libqgif.dylib dyld: loaded: /opt/local/share/qt4/plugins/imageformats/libqico.dylib dyld: loaded: /opt/local/share/qt4/plugins/imageformats/libqjpeg.dylib dyld: loaded: /opt/local/share/qt4/plugins/imageformats/libqmng.dylib dyld: loaded: /opt/local/lib/libmng.1.dylib dyld: loaded: /opt/local/share/qt4/plugins/imageformats/libqsvg.dylib dyld: loaded: /opt/local/share/qt4/plugins/imageformats/libqtiff.dylib digikam(46478)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) $ launchctl getenv DBUS_LAUNCHD_SESSION_BUS_SOCKET [...] dyld: loaded: /usr/lib/libDiagnosticMessagesClient.dylib dyld: loaded: /usr/lib/libDiagnosticMessagesClient.dylib dyld: loaded: /usr/lib/libicucore.A.dylib dyld: loaded: /usr/lib/libncurses.5.4.dylib /tmp/launch-SVHto8/unix_domain_listener }}} and yes, dbus is launched both as messagebus/root and current user, but it seems debug message/dyld loading are messing env -- Ticket URL: <https://trac.macports.org/ticket/42710#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X