• 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 20764
  • 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
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    What do you get if you run "ldd /cadence/tools/sev/lib/64bit/libvsacpp.so" ? Also what do you see if you do "ls -l /cadence/tools/sev/lib/64bit" ?

    Note that CentOS is not a supported OS, but I would expect it to work... I'm using RHEL6.5 which should be similar.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stevenyytan
    stevenyytan over 10 years ago

    Hi, Andrew,

    Thanks for your reply. In fact, I installed IC616 on the RHEL6.5 and 6.6. The same errors appeared, and then I changed to the CentOS. The IC616 was installed into the directory /eda/cadence. Thus when I run the command ldd /eda/cadence/tools/sev/lib/64bit/libvsacpp.so, the system reported

        linux-vdso.so.1 =>  (0x00007fffbf3ff000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fd119f7b000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fd119cf7000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fd119ae0000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fd11974c000)
        /lib64/ld-linux-x86-64.so.2 (0x0000003652400000)

    when I run the command ls -l /eda/cadence/tools/sev/lib/64bit, the system reported

    total 4548
    -rwxr-xr-x. 1 root root  410208 Feb  2  2014 libvpsl.so
    -rwxr-xr-x. 1 root root 4242600 Feb  2  2014 libvsacpp.so

    Thanks

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

    Strange. If you do "which virtuoso" what do you get? Also what does "virtuoso -debug3264 -64" report?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stevenyytan
    stevenyytan over 10 years ago

    Hi, Andrew,

    Thanks for your reply.

    when I do the command "which virtuoso", I get that

    /usr/bin/which: no virtuoso in (/cadence/tools/bin:/cadence/tools/dfII/bin/64bit:/cadence/tools/sev/lib/64bit:/eda/cadence/tools/bin:/eda/cadence/tools/dfII/bin/64bit:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/tan/bin)

    But I checked the file virtuoso is on the directory /cadence/tools/dfII/bin/64bit; Even if I changed the current directory to the directory /cadence/tools/dfII/bin/64bit, and do the command again, the system reported the same information. It is very strange.

    when I do the command virtuoso -debug3264 -64" , the system reported

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

    For the first command, it is very strange. Even if I do the command by using the super user, the system reported the same information.

    Thanks,

    steven

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stevenyytan
    stevenyytan over 10 years ago

    Hi, Andrew,

    I uninstalled IC616 and installed IC615, and then executed the command the "which virtuoso", the system reported 

    /cadence/IC615/tools/dfII/bin/64bit/virtuoso

    but when I executed the command "virtuoso -debug3264 -64" , the system reported

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

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • 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
  • Andrew Beckett
    Andrew Beckett over 10 years ago
    By the way, the wrappers also take care of picking either the 32 or 64 bit executables for you, depending on either command line switches provided or the value of the $CDS_AUTO_64BIT env var.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stevenyytan
    stevenyytan over 10 years ago

    Hi, Andrew,

    Thanks for your kind kind help. I reinstall the IC616. The previous problems were gone. But when I execute the command "virtuoso -64 &", the cds.log window appears very slowly, just like the following snapshot. I wait for more than one day, the window can appear successfully. In the file /etc/hosts, I added the line "127.0.0.1   localhost TAN", TAN is my machine name. Could you give me some suggestions to fix this problem?

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

    You should contact customer support - not going to be easy to debug this without seeing the problem. It should not be that slow!

    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