• 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. IC616

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 125
  • Views 20785
  • 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

IC616

stevenyytan
stevenyytan over 10 years ago

Hi, all,

I installed IC616 on CentOS 6.6 x86_64bit. When I run virtuoso -64, the system indicates the following information.

virtuoso: error while loading shared libraries: libvsacpp.so: can not open shared object file: No such file or directory.

I checked the directory /cadence/tools/sev/lib/64bit, and found that the file libvsacpp.so is there.

What is the problem about this, and how to fix it?

Thanks,

stevenyytan

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Ah, that explains it. Your $PATH is wrong. You should only have <ICinstDir>/tools/bin and <ICinstDir>/tools/dfII/bin in your path, not anything else (so none of the 64bit or 32bit dirs, and nothing from the other sub-directories in the installation). Otherwise you end up invoking the executables directly, not the wrappers that set up $LD_LIBRARY_PATH etc for you (which you don't need to set either, BTW) and so on - and because of this it doesn't know where to find the shared libraries.

    So correct your path and see what happens.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Ah, that explains it. Your $PATH is wrong. You should only have <ICinstDir>/tools/bin and <ICinstDir>/tools/dfII/bin in your path, not anything else (so none of the 64bit or 32bit dirs, and nothing from the other sub-directories in the installation). Otherwise you end up invoking the executables directly, not the wrappers that set up $LD_LIBRARY_PATH etc for you (which you don't need to set either, BTW) and so on - and because of this it doesn't know where to find the shared libraries.

    So correct your path and see what happens.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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