Dependency to unreleased versions
tittiatcoke at gmail.com
Tue Oct 22 09:42:23 BST 2013
On Monday 21 October 2013 19:10:49 Gilles Caulier wrote:
> Problem already reported here :
> It's completly different issue. Sound like client libraw code (as
> libkdcraw) need to be linked to libgomp when libraw OpenMP support is
> enabled. As libraw has already resolved OpenMP symbols at packaging
> time, why libkdcraw need again to resolve these ?
> OpenMP support is internal to libraw. Client code as libkdcraw do not
> use OpenMP API. I suspect something wrong in libraw packaging. Under
> Mageia, i cannot reproduce the problem...
Ben Cooksley asked me to validate this for openSUSE as that build.kde.org is
running openSUSE 12.3. libkdcraw always worked fine as that it had an up-to-
date internal libraw tree.
Now with the removal of the internal libraw tree, libkdcraw falls back on the
libraw that is provided by the distribution. And this causes the above
openSUSE 12.3 is using libraw 0.14.7 for libkdcraw for which the build fails
with the missing symbols. if I compile libkdcraw against the latest openSUSE
Factory (using libraw 0.15.4) then libkdcraw is compiling fine without any
issues. I validated both libraw packages and the only difference is the libraw
So I assume that libkdcraw needs libraw > 0.14.7
openSUSE KDE community maintainer
More information about the kde-core-devel