Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 16814
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IC5141 on RHEL5 64bit

pyohayo

Hello,

Can IC5141 work on RHEL5 64bit ?

Regards,

Pavel.

Parents
  • pyohayo

    Hi Quek,

    Thank you for response.

    When I try to run icfb, it doesn't work and following error message appears:

     /opt/cadence/IC5141/tools/dfII/bin/icfb.exe: relocation error: /opt/cadence/IC5141/tools/dfII/bin/icfb.exe: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference

    There are 2 versions of the file libc.so.6 on my system: first in the /lib directory and second is in the /lib64 directory. In the /lib/libc.so.6 the GLIBC_2.0 is defined:

    Here is the ouput of strings /lib/libc.so.6 | grep GLIBC :
    GLIBC_2.0
    GLIBC_2.1
    GLIBC_2.1.1
    GLIBC_2.1.2
    GLIBC_2.1.3
    GLIBC_2.2
    GLIBC_2.2.1
    GLIBC_2.2.2
    GLIBC_2.2.3
    GLIBC_2.2.4
    GLIBC_2.2.6
    GLIBC_2.3
    GLIBC_2.3.2
    GLIBC_2.3.3
    GLIBC_2.3.4
    GLIBC_2.4
    GLIBC_2.5
    GLIBC_PRIVATE

    The 64bit version of the libc.so.6 indeed doesn't define GLIBC_2.0:

    strings /lib64/libc.so.6 | grep GLIBC

    GLIBC_2.2.5
    GLIBC_2.2.6
    GLIBC_2.3
    GLIBC_2.3.2
    GLIBC_2.3.3
    GLIBC_2.3.4
    GLIBC_2.4
    GLIBC_2.5
    GLIBC_PRIVATE

    When I check shared libraries,  I see that it's 64-version of the libc.so.6, that is used. Here is the result of the ldd /bin/bash command:

            libtermcap.so.2 => /lib64/libtermcap.so.2 (0x0000003f8ac00000)
            libdl.so.2 => /lib64/libdl.so.2 (0x0000003f8a800000)
            libc.so.6 => /lib64/libc.so.6 (0x0000003f8a000000)
            /lib64/ld-linux-x86-64.so.2 (0x0000003f89c00000)

    It seems that icfb is wired to 64bit version of the libc.so.6, that doesn't define GLIBC_2.0.What could be solution of the problem. How to redirect icfb to 32bit version of the libc.so.6.

    My linux kernel is 2.6.18-164.11.1.el5. For compatibility with old kerneIs I also included following command in .bashrc file:

    export XD_ASSUME_KERNEL=2.4.1

    Regards.

    Pavel.

     

Reply
  • pyohayo

    Hi Quek,

    Thank you for response.

    When I try to run icfb, it doesn't work and following error message appears:

     /opt/cadence/IC5141/tools/dfII/bin/icfb.exe: relocation error: /opt/cadence/IC5141/tools/dfII/bin/icfb.exe: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference

    There are 2 versions of the file libc.so.6 on my system: first in the /lib directory and second is in the /lib64 directory. In the /lib/libc.so.6 the GLIBC_2.0 is defined:

    Here is the ouput of strings /lib/libc.so.6 | grep GLIBC :
    GLIBC_2.0
    GLIBC_2.1
    GLIBC_2.1.1
    GLIBC_2.1.2
    GLIBC_2.1.3
    GLIBC_2.2
    GLIBC_2.2.1
    GLIBC_2.2.2
    GLIBC_2.2.3
    GLIBC_2.2.4
    GLIBC_2.2.6
    GLIBC_2.3
    GLIBC_2.3.2
    GLIBC_2.3.3
    GLIBC_2.3.4
    GLIBC_2.4
    GLIBC_2.5
    GLIBC_PRIVATE

    The 64bit version of the libc.so.6 indeed doesn't define GLIBC_2.0:

    strings /lib64/libc.so.6 | grep GLIBC

    GLIBC_2.2.5
    GLIBC_2.2.6
    GLIBC_2.3
    GLIBC_2.3.2
    GLIBC_2.3.3
    GLIBC_2.3.4
    GLIBC_2.4
    GLIBC_2.5
    GLIBC_PRIVATE

    When I check shared libraries,  I see that it's 64-version of the libc.so.6, that is used. Here is the result of the ldd /bin/bash command:

            libtermcap.so.2 => /lib64/libtermcap.so.2 (0x0000003f8ac00000)
            libdl.so.2 => /lib64/libdl.so.2 (0x0000003f8a800000)
            libc.so.6 => /lib64/libc.so.6 (0x0000003f8a000000)
            /lib64/ld-linux-x86-64.so.2 (0x0000003f89c00000)

    It seems that icfb is wired to 64bit version of the libc.so.6, that doesn't define GLIBC_2.0.What could be solution of the problem. How to redirect icfb to 32bit version of the libc.so.6.

    My linux kernel is 2.6.18-164.11.1.el5. For compatibility with old kerneIs I also included following command in .bashrc file:

    export XD_ASSUME_KERNEL=2.4.1

    Regards.

    Pavel.

     

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.