Hi Ben,
On 13 Dec 2014, at 21:39 , Ben Cooksley wrote:
> This is where DYLD_LIBRARY_PATH comes in - and it is a variable the CI
> scripts should already be setting for you.
yes, of course!
:)
Thanks for the reminder!
Marko
___
Kde-frameworks-devel ma
On Sun, Dec 14, 2014 at 4:47 AM, Marko Käning 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
> Op
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
Hi,
on my OSX/CI system I realised that qtdiag reports that it cannot resolve
certain transfer methods and wonder which system path hasn’t been set
correctly here (see below).
This e.g. doesn’t allow me to run Trojita on the console [1], but its tests
at build time run flawlessly!
Any ideas?
Gr
