Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 3059
  • 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

PVS fails with version `GLIBCXX_3.4.26' not found

thspaet

Hello,

I'm trying to make PVS (PVS21.12.000-ISR2_lnx86.tgz) work with IC618 (IC06.18.270_lnx86.tgz), but so far I always with this error:

/eda/cadence/2022-2023/lnx86/PVS211/tools.lnx86/pvs/bin/64bit/pvsvirt: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /eda/cadence/2022-2023/lnx86/PVS211/tools.lnx86/pvs/bin/64bit/pvsvirt)

pvsvirt is linked against libstdc++.so.6 but the version, that comes with AlmaLinux8 or rhel8 (i checked them both) only provides up to GLIBCXX_3.4.25. Trying to install the corresponding package from AlmaLinux9 or rhel9 is not an option, because it leads to a dependency nightmare.

As a university chair we receive Cadence through Europractice and it provides two ways to install Cadence.

a) Prepackaged archives that come with a simple script, that simply extracts those archives into a specified folder. Nothing fancy. So far I preferred this way, because it's way easier. But thanks to error I thought maybe someone messed things up during the packaging, so I also tried the other way.

b) The normal way with iscape. But because EP-customers don't have access to the official data sources, there is a small detour by using EP-packed packages again.

Both ways lead to the same error and now I'm out of ideas.

Maybe somebody else ran into a similar problem and can help.

Kind regards,

Thorsten Spätling

  • Dear Thorsten,

    have you checked whether your LD_LIBRARY_PATH is set correctly, i.e., that PVS does not load libraries from an incorrect location.
    I would suggest that you unset LD_LIBRARY_PATH and check if that helps.

    Regards

    Matthias

  • in reply to mschw

    Thorsten,

    Can you try running (from a terminal):

    UNIX> pvsvirt -opt3264 -debugger3264 ldd

    pvsvirt:----------------------------------------------------------
    pvsvirt: INFO: Debugging: "/apps/PVS211/21.12.000/tools.lnx86/pvs/bin/64bit/pvsvirt"
    pvsvirt:
    pvsvirt: Once debugger starts up run with:
    pvsvirt:
    pvsvirt: run
    pvsvirt:----------------------------------------------------------

    pvsvirt: INFO: Launching debugger: ldd /apps/PVS211/21.12.000/tools.lnx86/pvs/bin/64bit/pvsvirt

    linux-vdso.so.1 => (0x00007ffc1c7a3000)
    libelf.so.1 => /lib64/libelf.so.1 (0x00002b589b2ac000)
    libutil.so.1 => /lib64/libutil.so.1 (0x00002b589b4c4000)
    libnsl.so.1 => /lib64/libnsl.so.1 (0x00002b589b6c7000)
    libstdc++.so.6 => /apps/PVS211/21.12.000/tools.lnx86/lib/64bit/libstdc++.so.6 (0x00002b589b0ad000)
    librt.so.1 => /lib64/librt.so.1 (0x00002b589b8e1000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b589bae9000)
    libdl.so.2 => /lib64/libdl.so.2 (0x00002b589bd05000)
    libm.so.6 => /lib64/libm.so.6 (0x00002b589bf09000)
    libc.so.6 => /lib64/libc.so.6 (0x00002b589c20b000)
    /lib64/ld-linux-x86-64.so.2 (0x00002b589b088000)
    libgcc_s.so.1 => /apps/PVS211/21.12.000/tools.lnx86/lib/64bit/libgcc_s.so.1 (0x00002b589b288000)
    libz.so.1 => /lib64/libz.so.1 (0x00002b589c5d8000)

    It should be resolving the libstdc++ shared library from the installation itself - can you check to see if that's what you get?

    Andrew

  • in reply to Andrew Beckett

    Thank you Matthias and Andrew over the weekend it already dawned on me, that I'm hunting for an error I introduced myself. So when I execute Andrew's command it looks similar and yes, libstdc++ is resolved into the installation folder.

    In hindsight it's totally obvious. When PVS is executed within Cadence, Cadence sets the necessary environmental variables, therefore PVS runs. If I do it on my own those variables aren't set and PVS complains. Makes sense Slight smile

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.