[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [digikam] [Bug 365331] digikam not loading because rpath information missing from libQt5Qml, libQt5S
From:       Mario Frank <bugzilla_noreply () kde ! org>
Date:       2017-02-28 15:48:32
Message-ID: bug-365331-17878-Iagiel58wb () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=365331

Mario Frank <mario.frank@uni-potsdam.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mario.frank@uni-potsdam.de

--- Comment #6 from Mario Frank <mario.frank@uni-potsdam.de> ---
(In reply to RJVB from comment #5)
> Edit: it would *seem* that the issue has resolved itself in 5.3.0 .
> 
> I agree something was wrong, but digiKam is the only application where I've
> seen this happen with my build settings, and only for a few Qt libraries.
> I don't know how the AppImage stuff is finagled together, but I'm not using
> that. I'm just using unpatched CMake files and everything KF5 is built with
> the settings required to apply full rpaths to all binaries. Qt5 itself is
> built that way too.
> 
> I'd agree the problem was fully on my end if I saw this happening to all Qt
> libraries (in DK or in other applications too), but that isn't the case.
> 
> The simplest explanation would be that somehow the rpath information is
> dropped for the affected Qt libraries

Is the problem resolved now? Can you test this with current master branch
(version 5.5.0)?

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]