On Apr 13, 2017, at 09:46:46, Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
On Thu, Apr 13, 2017 at 3:19 PM, Tom Kacvinsky <tom.kacvinsky@suse.com> wrote:
Hmmm, I have never seen this in a dynamic section of a shared library:
0x000000006ffffffb (FLAGS_1) Flags: NODEFLIB
I will research this to see what the effect of this flag is. I no wonder if there is something in process of using TBB that forces this flag to be in effect.
Can you see if the build process for the library in question has this option set: -z nodefaultlib. If gcc/g++ is used as the linker, the option would be -Wl,-z,nodefaultlib (or use of -Xlinker instead of -Wl)
See "man 1 ld" for more information.
Not that I see. But it does specify: -fopenmp
The build i defined by Intel. They use both -fopenmp and pthread and tbb.
-fopenmp just instructs the compiler to honor OpneMP pragmas in the code and then link in an OpenMP library (could be Intel's or GCC's OpenMP library). What I would do is to run readelf -d on each of the libraries that is linked in and see if any of them have the NODEF option. And I would also check to see if TBB offers it's own pthreads library. I don't know enough about TBB to know any better. Since you are using TBB, you might want to file a case with Intel to see if they're doing anything special behind the scenes. They might have a linker script they're using the @<file> option, where <file> contains additional linker options. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org