|
After upgrading to opencv 3.4.1-1 I've got the error message
symbol lookup error: /usr/lib/libopencv_core.so.3.4: undefined symbol: _ZN3tbb10interface78internal15task_arena_base24internal_max_concurrencyEPKNS0_10task_arenaE downgrading to opencv 3.4.0-2 solved the problem (archlinux) Jürgen -- Jürgen Blumenschein, eMail: [hidden email] Homepage: http://members.dokom.net/blumenschein Am Quartus 17 D-44149 Dortmund Tel.: +49 231 7217321, Handy: +49 176 5591 4562 public key: http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc |
|
Hi, This is a linking problem on your system, not a compilation one. This can be typically : 1/ a cmake cache to cleanup before to compile. 2/ a wrong linker configuration done by OpenCV install. There is nothing special to tune in digiKam here... Gilles Caulier 2018-03-11 11:29 GMT+01:00 Jürgen Blumenschein <[hidden email]>: After upgrading to opencv 3.4.1-1 I've got the error message |
|
In reply to this post by Jürgen Blumenschein
On 03/11/2018 11:29 AM, Jürgen Blumenschein wrote:
> After upgrading to opencv 3.4.1-1 I've got the error message > > symbol lookup error: /usr/lib/libopencv_core.so.3.4: undefined symbol: > _ZN3tbb10interface78internal15task_arena_base24internal_max_concurrencyEPKNS0_10task_arenaE > > > downgrading to opencv 3.4.0-2 solved the problem (archlinux) > Hi Last Arch Opencv works with this DK version for me. https://aur.archlinux.org/packages/digikam-git/ -- Maderios |
|
In reply to this post by Jürgen Blumenschein
On dimanche 11 mars 2018 11:29:53 CET Jürgen Blumenschein wrote:
> After upgrading to opencv 3.4.1-1 I've got the error message > > symbol lookup error: /usr/lib/libopencv_core.so.3.4: undefined symbol: > _ZN3tbb10interface78internal15task_arena_base24internal_max_concurrencyEPKNS > 0_10task_arenaE > > downgrading to opencv 3.4.0-2 solved the problem (archlinux) > > Jürgen Typical symptom of a version mismatch. Either the newer version changed the signature of the funtion, or the compiler (settings) changed. That name you see is the compiler-mangled version of the function name. And C++ compilers have to use mangled names, as they have to be able to distinguish function overloads (funtions with the same name, but different parameters). If the compiler mangles the name differently (for whatever reason, even some command line options can cause it), you'll get such errors. Remco |
| Free forum by Nabble | Edit this page |
