OpenCL* for CPU
Ask questions and share information on Intel® SDK for OpenCL™ Applications and OpenCL™ implementations for Intel® CPU.
Announcements
This forum covers OpenCL* for CPU only. OpenCL* for GPU questions can be asked in the GPU Compute Software forum. Intel® FPGA SDK for OpenCL™ questions can be ask in the FPGA Intel® High Level Design forum.
1719 Discussions

libclang_compiler.so: error: symbol lookup error: undefined symbol: RegisterGlobalAtExitNotification

Rohit_R_
Beginner
‎01-17-2018 04:54 AM
679 Views

Hi,

I get the following runtime error on Linux.

/opt/intel/opencl-1.2-6.4.0.25/lib64/libclang_compiler.so: error: symbol lookup error: undefined symbol: RegisterGlobalAtExitNotification (fatal)

Which library should I link with to resolve these errors?

Thanks,

Rohit

0 Kudos

Link Copied

2 Replies
Shubha_R_Intel
Employee
‎01-17-2018 03:37 PM
679 Views

Can you kindly give more information about your system configuration ? I.e. which OS you are using, which compiler, etc....Meanwhile we will try to reproduce your issue.

0 Kudos
Copy link
Rohit_R_
Beginner
‎01-17-2018 09:25 PM
679 Views

Hi,

Please find additional details below.

Configuration:
Ubuntu 14.04 LTS 64 bit version. I have installed Intel OpenCL Runtime 1.2-6.4.0.25. I have Intel OpenCL CPU device listed in clinfo on Linux.

I am facing this issue when we run our application that was compiled with Clang++ version 3.7.

Rohit

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.