9 Replies Latest reply on Feb 4, 2010 4:42 AM by gapon

    OpenCL issues working on CentOS 5.4 x64.

      Library woes.

      I'm trying to run a few of the samples and get my OpenCL development environment working in CentOS 5.4 x64.  I have run into some issues that prevent it from working as expected.  Errors are shown below:

      [tyler@tyler-workstation x86_64]# ldd CLInfo
      ./CLInfo: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by ./CLInfo)
              libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003975200000)
              libdl.so.2 => /lib64/libdl.so.2 (0x0000003974e00000)
              libOpenCL.so => /usr/local/ati/lib/x86_64/libOpenCL.so (0x00002ae12115e000)
              libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003985400000)
              libm.so.6 => /lib64/libm.so.6 (0x0000003974a00000)
              libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003982000000)
              libc.so.6 => /lib64/libc.so.6 (0x0000003974600000)
              /lib64/ld-linux-x86-64.so.2 (0x0000003973600000)
              librt.so.1 => /lib64/librt.so.1 (0x0000003975600000)
      [tyler@tyler-workstation x86_64]# ./NBody
      Error: clGetPlatformIDs failed. Error code : unknown error code

      [root@tyler-workstation x86_64]# echo $LD_LIBRARY_PATH

      My stream SDK has been installed to /usr/local/ati/lib/x86_64.

      I was able to run make in my the top level directory(/usr/local/ati) and it exited with no errors, it's when I try to run the sample executables that I run into issues.

      [root@tyler-workstation ati]# echo $LD_LIBRARY_PATH

      So that said, it seems the issue is with CLInfo wanting a specific GLIBC version(3.4.9).  Is there any workaround?


      Thanks in advance!


        • OpenCL issues working on CentOS 5.4 x64.


                It looks like you are facing ICD issue.

                You must register the OpenCL ICD; otherwise, samples and other applications will fail to
          execute if this is not done. To register the ICD:
          a. If one does not exist, create a folder /usr/lib/OpenCL/vendors.
          b. Create the /usr/lib/OpenCL/vendors folder, if does not already exist.
          c. Symlink [INSTALLDIR]/x86/libatiocl32.so into the vendors folder:
          sudo ln -sf [INSTALLDIR]/x86/libatiocl32.so /usr/lib/OpenCL/vendors/libatiocl32.so
          d. For 64-bit installations, you also must symlink
          [INSTALLDIR]/x86_64/libatiocl64.so to the vendors folder:
          sudo ln -sf [INSTALLDIR]/x86_64/libatiocl64.so /usr/lib/OpenCL/vendors/libatiocl64.so
          Samples and other applications will fail to execute if this is not done.

          • OpenCL issues working on CentOS 5.4 x64.

            I've ran into the very same problem on Red Hat WS 5.3. It turns out that OpenCL SDK 2.0 requires GCC 4.3.2 or higher (4.4). Meanwhile Red Hat 5.3 (and so does CentOS 5.3) comes with GCC 4.1.2. GLIBCXX_3.4.9 is available starting with GCC 4.3.2. Fortunately, Red Hat provides GCC 4.4 via the "Technology Preview" program:


            I'm not sure if this would apply to CentOS users.

            By the way, I suspect this was a reason why the production version of OpenCL SDK 2.0 dropped Red Hat from a list of supported systems (it was in the earlier 'beta' version of SDK which only required GCC 4.1.2).

            Anyone knows what's special in the recent version of GCC?