On Sun, Dec 14, 2014 at 4:47 AM, Marko Käning <mk-li...@email.de> wrote: > Turns out that this COULD BE due to the fact that qtdiag grabs the system’s > openssl executable > in /usr/bin instead of the one installed via MacPorts in /opt/local/bin... > --- > MVM2:scripts marko$ /usr/bin/openssl > OpenSSL> version > OpenSSL 0.9.8za 5 Jun 2014 > --- > > Since the system’s openssl version is below 1.0 the methods can’t be resolved! > > > > Wondering how I could make qtdiag find the one installed in /opt/local/bin, > as this > --- > $ PATH=/opt/local/bin > /opt/kde/install/darwin/mavericks/clang/kf5-qt5/qt5/inst/bin/qtdiag > $ echo $PATH > /Users/marko/bin:/opt/local/bin:/opt/local/sbin:/opt/local/libexec/gnubin:/opt/local/lib/mysql55/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin > --- > is NOT doing the job, as the PATH env var already has /opt/local/bin first.
This is where DYLD_LIBRARY_PATH comes in - and it is a variable the CI scripts should already be setting for you. Thanks, Ben > _______________________________________________ > Kde-frameworks-devel mailing list > Kde-frameworks-devel@kde.org > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel