From kde-release-team  Tue Oct 22 08:42:23 2013
From: Raymond Wooninck <tittiatcoke () gmail ! com>
Date: Tue, 22 Oct 2013 08:42:23 +0000
To: kde-release-team
Subject: Re: Dependency to unreleased versions
Message-Id: <1680616.GYtxuqeJjS () hqvmt4xx20 ! eur ! cchbc ! com>
X-MARC-Message: https://marc.info/?l=kde-release-team&m=138243138616588

On Monday 21 October 2013 19:10:49 Gilles Caulier wrote:
> Problem already reported here :
> 
> https://bugs.kde.org/show_bug.cgi?id=326368
> 
> 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...
> 
Gilles, 

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 
indicated problem. 

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 
version. 

So I assume that libkdcraw needs libraw > 0.14.7 

Regards

Raymond
openSUSE KDE community maintainer
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team