• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. IC5141 on RHEL5 64bit

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 16811
  • 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
pyohayo over 13 years ago

Hello,

Can IC5141 work on RHEL5 64bit ?

Regards,

Pavel.

  • Cancel
  • Quek
    Quek over 13 years ago

    Hi Pavel

    Yes, it works. Only "layout" executable works in 64bits. The rest will remain in 32bits on the 64bits OS.


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • pyohayo
    pyohayo over 13 years ago

    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.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Pavel,

    I only see that error if using a really old version of IC5141 (e.g. the Base CD version, or USR1). Using USR6 or a recent hotfix works fine. You should make sure you're using a recent enough build.

    I have been running IC5141 on RHEL5 for about 4.5 years or so, and the only real issue is with cdsdoc (there's a solution on Cadence Online Support for how to make that work too, which I wrote). That said, IC5141 is not actually supported on RHEL5 (which means it is not tested on that OS) - but in practice, it woks fine.

    By the way, the XD_ASSUME_KERNEL won't do anything, I believe, because it should be LD_ASSUME_KERNEL. However, you should not set that on RHEL5 because all sorts of things will break if you do that!

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • pyohayo
    pyohayo over 13 years ago

    Andrew, thank you for response.

    What upgrade is better - USR or hotfix (ISR, QSR). As I've heared only USRs modifications are 100% tested. But ISRs are more recent - the last USR - USR6 dates 2008, whereas there were ISRs in 2009 (or even later).

    Regards,

    Pavel.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Pavel,

    I would suggest that the latest ISR is the most sensible - there have been a lot of fixes over the intervening 3-4 years since the last USR.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • pyohayo
    pyohayo over 13 years ago
    Ok, thank you Andrew.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information