[Bug 274940] New: digikam freezes when using "sharpen: refocus" (cpu 100%)

[Peter Albrecht-2]

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

           Summary: digikam freezes when using "sharpen: refocus" (cpu
                    100%)
           Product: digikam
           Version: 1.9.0
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Image Editor
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


Version:           1.9.0 (using KDE 4.6.2)
OS:                Linux

Using the sharpening method "Refocus" seems to initiate a closed loop and
renders this sharpening method unuseable.

"Simple Sharpening" works flawless.

Reproducible: Always

Steps to Reproduce:
1. start digikam
2. select image and open it in "Image Editor (F4)
3. in menu: "Enhance" -> "Sharpen..."
4. select "method = Refocus"
5. click "Try"

Actual Results:  
- mouse cursor changes to "please wait, I'm working"
- the progressbar in Image Editor keeps stuck at "0%"
- cpu-usage of digikam goes up to 100% and stays there
- nothing else happens for 5 minutes and more (in digikam 1.2.0 refocus
finished within 60 seconds)

Expected Results:  
digikam calculates and shows preview of current refocus settings

To test with a clean profile, I have also deleted every "*digikam*"-file in
"~/.kde4/". But that did not help.

Enabling every digikam-entry in kdebugdialog shows me the following two lines
at STDOUT:

------------ 8< ------------
digikam(4992)/digikam (core) Digikam::EditorToolThreaded::slotEffect: Preview
"Sharpen"  started...
digikam(4992)/digikam (core) Digikam::RefocusFilter::refocusImage:
RefocusFilter::Compute matrix...
------------ >8 ------------

After >30 seconds the following lines are added, but I think they are not
important:
------------ 8< ------------
digikam(5147)/khtml (caret) DOM::Selection::moveTo: Selection[ Position( 0x0
"null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position(
0x0 "null" : 0 ) 1 ] Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
digikam(5147)/khtml (caret) DOM::Selection::validate: Selection[ Position( 0x0
"null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position(
0x0 "null" : 0 ) 1 ] 0
digikam(5147)/khtml (caret) DOM::Selection::validate: [character:baseIsStart]
true Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
digikam(5147)/kio (Slave) KIO::Slave::kill: killing slave pid 5162 (
"digikamdates://" )
[...]
------------ >8 ------------

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
          Component|Image Editor                |Refocus
            Product|digikam                     |digikamimageplugins




--- Comment #1 from Gilles Caulier <caulier gilles gmail com>  2011-06-07 10:47:15 ---
Not reproducible here. As refocus tool run in a separated thread, can you run
digiKam through gdb and look if a crash appears ?

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

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





--- Comment #2 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-06-11 16:22:39 ---
If it does not crash but runs at 100% CPU, please:
- find out the process id of digikam (system monitor, or ps -ax | grep digikam)
- run "gdb att <id>"
- post the output of "thr appl all bt"

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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





--- Comment #3 from Peter Albrecht <px79 crazymonkeys de>  2011-06-11 22:31:59 ---
Created an attachment (id=60915)
 --> (http://bugs.kde.org/attachment.cgi?id=60915)
gdb output for "thr appl all bt"

This file contains the gdb output of "thr appl all bt", attached to the "100%
cpu" state of digikams refocus.

According to top (using thread view), the 100% cpu thread is 13667. That must
be thread 2 in gdb.txt. Main process id was 13639.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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





--- Comment #4 from Peter Albrecht <px79 crazymonkeys de>  2011-06-11 22:51:27 ---
Do you need debug output for libclapack, too?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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


Peter Albrecht <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #60915|0                           |1
        is obsolete|                            |




--- Comment #5 from Peter Albrecht <px79 crazymonkeys de>  2011-06-12 07:58:51 ---
Created an attachment (id=60919)
 --> (http://bugs.kde.org/attachment.cgi?id=60919)
gdb output for "thr appl all bt" as requested in comment #2 (with clapack debug
symbols)

This time with clapack debug symbols.

The 100% cpu thread has ID 31101. Process ID was 26148.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

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





--- Comment #6 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-06-14 22:18:57 ---
Code is running inside dgesv from clapack. So at first it looks like normal
work being done.
I cannot seem to reproduce the problem with a simle test.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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





--- Comment #7 from Peter Albrecht <px79 crazymonkeys de>  2011-06-17 22:39:07 ---
I did some more debugging tonight:

The infinity loop seems to be at
"/var/tmp/portage/sci-libs/clapack-3.2.1-r4/work/clapack-3.2.1-CMAKE/INSTALL/dlamch.c"
lines 348 to 355.

The source code is:
------------------------ CODE ------------------------
    lt = 0;
    a = 1.;
    c__ = 1.;


/* +       WHILE( C.EQ.ONE )LOOP */
L30:
    if (c__ == one) {
        ++lt;
        a *= lbeta;
        c__ = dlamc3_(&a, &one);
        d__1 = -a;
        c__ = dlamc3_(&c__, &d__1);
        goto L30;
    }
/* +       END WHILE */
------------------------ /CODE ------------------------
and it is entered with:
   one = 1
   lbeta = 0


The reason might be found in this bug report:
https://mailman.cae.wisc.edu/pipermail/bug-octave/2009-November/016247.html

An important sentence in one of the answers:
 "the SLAMCH and DLAMCH routines are sensitive to compiler optimizations."

And since I'm using a gentoo linux, I have plenty of options to "kill" DLAMCH
with various compiler options. :(

I guess it is a gentoo bug now and should further be handled at
bugs.gentoo.org. What do you think?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Francesco Riosa-2]

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


Francesco Riosa <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #8 from Francesco Riosa <francesco+kde pnpitalia it>  2011-06-17 23:01:26 ---
It's not a Gentoo bug either, if you use something else than "-O2 -pipe
-fomit-frame-pointer".
In particular using flags which affect math precision on all packages is simply
plain wrong, packages which can benefit from these generally set them by
themself.

you can still open a bug on gentoo bugzilla asking for them to filter-flags
providing also a `emerge --info sci-libs/clapack`

thank you for investigating this issue

http://en.gentoo-wiki.com/wiki/Safe_Cflags (unofficial)

(In reply to comment #7)

> I did some more debugging tonight:
>
> The infinity loop seems to be at
> "/var/tmp/portage/sci-libs/clapack-3.2.1-r4/work/clapack-3.2.1-CMAKE/INSTALL/dlamch.c"
> lines 348 to 355.
>
> The source code is:
> ------------------------ CODE ------------------------
>     lt = 0;
>     a = 1.;
>     c__ = 1.;
>
>
> /* +       WHILE( C.EQ.ONE )LOOP */
> L30:
>     if (c__ == one) {
>         ++lt;
>         a *= lbeta;
>         c__ = dlamc3_(&a, &one);
>         d__1 = -a;
>         c__ = dlamc3_(&c__, &d__1);
>         goto L30;
>     }
> /* +       END WHILE */
> ------------------------ /CODE ------------------------
> and it is entered with:
>    one = 1
>    lbeta = 0
>
>
> The reason might be found in this bug report:
> https://mailman.cae.wisc.edu/pipermail/bug-octave/2009-November/016247.html
>
> An important sentence in one of the answers:
>  "the SLAMCH and DLAMCH routines are sensitive to compiler optimizations."
>
> And since I'm using a gentoo linux, I have plenty of options to "kill" DLAMCH
> with various compiler options. :(
>
> I guess it is a gentoo bug now and should further be handled at
> bugs.gentoo.org. What do you think?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Andreas K. Huettel]

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


Andreas K. Huettel <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #9 from Andreas K. Huettel <dilfridge gentoo org>  2011-06-18 02:17:38 ---
(In reply to comment #8)
> It's not a Gentoo bug either, if you use something else than "-O2 -pipe
> -fomit-frame-pointer".
> In particular using flags which affect math precision on all packages is simply
> plain wrong, packages which can benefit from these generally set them by
> themself.
>
> you can still open a bug on gentoo bugzilla asking for them to filter-flags
> providing also a `emerge --info sci-libs/clapack`

Gentoo clapack maintainer here :). You can also just tell us your CFLAGS here,
I'm watching digikam-devel on the kde bugzilla anyway.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #10 from Gilles Caulier <caulier gilles gmail com>  2011-06-18 09:40:52 ---
Note : in OPenCV library, there is a 3rdparty clapack code embeded. As they use
Cmake too, perhaps some compilation tunes are done to prevent a similar
problem.

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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





--- Comment #11 from Peter Albrecht <px79 crazymonkeys de>  2011-06-18 14:12:50 ---
# emerge --info: (see also the following attachment)
---------------- 8< ----------------
[...]
CFLAGS="-O2 -march=core2 -msse4.1 -pipe"
[...]
CXXFLAGS="-O2 -march=core2 -msse4.1 -pipe"
[...]
---------------- >8 ----------------

If debugging, I add "-ggdb" to CFLAGS and CXXFLAGS and add "nostrip" to
FEATURES. The Problem occurs in "debug-" and "non-debug-mode".


# cat /proc/cpuinfo
---------------- >8 ----------------
[...]
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz
[..]
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc
arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2
ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dts tpr_shadow vnmi flexpriority
[...]
---------------- 8< ----------------

According to this Wiki-Article
(http://en.gentoo-wiki.com/wiki/Safe_Cflags/Intel#Core_2_Duo.2FQuad.2C_Xeon_51xx.2F53xx.2F54xx.2F3360.2C_Pentium_Dual-Core_T23xx.2B.2FExxxx.2C_Celeron_Dual-Core)
those use flags should be ok.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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





--- Comment #12 from Peter Albrecht <px79 crazymonkeys de>  2011-06-18 14:14:59 ---
Created an attachment (id=61114)
 --> (http://bugs.kde.org/attachment.cgi?id=61114)
The emerge settings media-gfx/digikam-1.9.0 and sci-libs/clapack-3.2.1-r4 are
currently compiled with

Output of "emerge --info".

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #13 from Gilles Caulier <caulier gilles gmail com>  2011-06-18 14:21:52 ---
Look into OpenCV 3rdparty. CLapack is here and source code is compiled with
this options :

https://opencvlibrary.svn.sourceforge.net/svnroot/opencvlibrary/trunk/opencv/3rdparty/lapack/CMakeLists.txt

... look at lines:

    set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-parentheses")
    set_source_files_properties(dlamch.c slamch.c PROPERTIES COMPILE_FLAGS
"-ffloat-store -O0")

perhaps i need to turn on these options with GCC...

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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





--- Comment #14 from Peter Albrecht <px79 crazymonkeys de>  2011-06-18 14:29:14 ---
Created an attachment (id=61115)
 --> (http://bugs.kde.org/attachment.cgi?id=61115)
Output of "echo | gcc -dM -E - -march=native"

According to http://en.gentoo-wiki.com/wiki/Safe_Cflags#-march.3Dnative this
would be the settings, gcc would pic automatically.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Francesco Riosa-2]

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





--- Comment #15 from Francesco Riosa <francesco+kde pnpitalia it>  2011-06-18 15:28:19 ---
Created an attachment (id=61117)
 --> (http://bugs.kde.org/attachment.cgi?id=61117)
emerge --info sci-libs/clapack

(In reply to comment #11)

> # emerge --info: (see also the following attachment)
> ---------------- 8< ----------------
> [...]
> CFLAGS="-O2 -march=core2 -msse4.1 -pipe"
> [...]
> CXXFLAGS="-O2 -march=core2 -msse4.1 -pipe"
> [...]
> ---------------- >8 ----------------
>
> If debugging, I add "-ggdb" to CFLAGS and CXXFLAGS and add "nostrip" to
> FEATURES. The Problem occurs in "debug-" and "non-debug-mode".
>
>
> # cat /proc/cpuinfo
> ---------------- >8 ----------------
> [...]
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 23
> model name      : Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz
> [..]
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc
> arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2
> ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dts tpr_shadow vnmi flexpriority
> [...]
> ---------------- 8< ----------------
>
> According to this Wiki-Article
> (http://en.gentoo-wiki.com/wiki/Safe_Cflags/Intel#Core_2_Duo.2FQuad.2C_Xeon_51xx.2F53xx.2F54xx.2F3360.2C_Pentium_Dual-Core_T23xx.2B.2FExxxx.2C_Celeron_Dual-Core)
> those use flags should be ok.

Same CPU here, but using a 64bit environment, recompiled sci-libs/clapack with
C*FLAGS="-O2 -march=core2 -msse4.1 -pipe -ggdb", gcc-4.5.2 and the loop is not
reproducible.
Same does apply using gcc-4.6.0 and CFLAGS as in attached emerge --info.

Speaking of digikam-2.0 from git because I've problem recompiling digikam-1.9
alone with gcc-4.5.2 (need to rebuild kexif and possibly other)

may be this problem only related to 32 bit builds?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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





--- Comment #16 from Peter Albrecht <px79 crazymonkeys de>  2011-06-18 22:02:31 ---
(In reply to comment #13)

> Look into OpenCV 3rdparty. CLapack is here and source code is compiled with
> this options :
>
> https://opencvlibrary.svn.sourceforge.net/svnroot/opencvlibrary/trunk/opencv/3rdparty/lapack/CMakeLists.txt
>
> ... look at lines:
>
>     set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-parentheses")
>     set_source_files_properties(dlamch.c slamch.c PROPERTIES COMPILE_FLAGS
> "-ffloat-store -O0")

As a test, I set "-O2" in C*FLAGS to "-O0" in /etc/make.conf and recompiled
"sci-libs/clapack-3.2.1-r4".
=> the infinite loop seems to be eleminated and digikam's Refocus plugin (using
clapack) works flawless.

So I think the following line might fix this bug:
set_source_files_properties(dlamch.c slamch.c PROPERTIES COMPILE_FLAGS "-O0")

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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





--- Comment #17 from Peter Albrecht <px79 crazymonkeys de>  2011-06-18 22:10:24 ---
(In reply to comment #15)
> Same CPU here, but using a 64bit environment, recompiled sci-libs/clapack with
> C*FLAGS="-O2 -march=core2 -msse4.1 -pipe -ggdb", gcc-4.5.2 and the loop is not
> reproducible.
> Same does apply using gcc-4.6.0 and CFLAGS as in attached emerge --info.
>
> Speaking of digikam-2.0 from git because I've problem recompiling digikam-1.9
> alone with gcc-4.5.2 (need to rebuild kexif and possibly other)
>
> may be this problem only related to 32 bit builds?

I'm using gcc-4.4.5, which also _might_ be the critical difference. But in
reference to comment #8, the 32 bit system seems more likely.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Andreas K. Huettel]

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





--- Comment #18 from Andreas K. Huettel <dilfridge gentoo org>  2011-06-19 22:38:39 ---
(In reply to comment #16)
> set_source_files_properties(dlamch.c slamch.c PROPERTIES COMPILE_FLAGS "-O0")

This has been patched in sci-libs/clapack-3.2.1-r6 - keyword that and you
should be fine. I'll raise the dependencies as soon as it becomes stable.
From the Gentoo side this bug can be closed.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Peter Albrecht-2]

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





--- Comment #19 from Peter Albrecht <px79 crazymonkeys de>  2011-06-20 19:10:55 ---
I keyworded sci-libs/clapack-3.2.1-r6 and emerged it, but the infinite loop is
still there.

 # ebuild /usr/portage/sci-libs/clapack/clapack-3.2.1-r6.ebuild configure
 # cd /var/tmp/portage/sci-libs/clapack-3.2.1-r6
 # grep -nHrD skip "set_source_files_properties" .
gives me:
> ./work/clapack-3.2.1-CMAKE/SRC/CMakeLists.txt:359:   set_source_files_properties(dlamch.c slamch.c PROPERTIES COMPILE_FLAGS "-ffloat-store -O0")

But is this the correct directory/CMakeList.txt? Because
 # find -iname "dlamch*"
gives me:
> ./work/clapack-3.2.1-CMAKE/INSTALL/dlamch.c

=> "set_source_files_properties" is in SRC-Directory, but the specified file is
in INSTALL-Directory

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel