Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 8313
  • 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

Making IC6.1.7 run on RHEL8

MtHopper

Hi All,

I am trying to run IC 6.1.7 on RHEL8 and I get the following error message:

WARNING This OS does not appear to be a Cadence supported Linux configuration.
2023/07/18 18:55:14 For more info, please run CheckSysConf in <cdsRoot/tools.lnx86/bin/checkSysConf <productId>
virtuoso: ERROR: The command .../eda/cadence/ic/lnx86/6.17.722/share/oa/bin/sysname returned an error status:
unknown
virtuoso: INFO: Note that OpenAccess (OA) requires running the Configure phase.
virtuoso: See the "OpenAccess Installation and Configuration Guide" before
virtuoso: you complete the configuration step. This manual is included with
virtuoso: the Cadence product documentation.

[1]+ Exit 1

I know that IC 6.1.7 is not supported on RHEL8, but I am wondering if there is a way to get past the error message highlighted above and still run Virtuoso 6.1.7 (accepting the risks...)

Thanks!

  • I think there's not a huge chance of getting this working. You might have needed to set this:

    setenv OA_UNSUPPORTED_PLAT linux_rhel50_gcc48x

    However, the first issue I faced when trying this just now was that cds_root fails to run because it's a 32-bit executable and the RHEL8 machine I had access to doesn't have even the 32-bit glibc installed. It's really not a supported flow (even IC6.1.8 is not officially supported on RHEL8, because it's not routinely tested, but fixes were made after IC6.1.8 ISR24 to allow it to run).

    I would suggest using IC6.1.8 (a recent hotfix) or the latest IC23.1 release (which is officially supported on RHEL8) rather than trying to use a release which had its last hotfix nearly 5 years ago.

    Regards,

    Andrew

  • in reply to Andrew Beckett

    Thank you for your suggestions. I'll try them out and report back. I'll also need to check if the PDK we're using is compatible with IC6.1.8 (compared to IC6.1.7).

  • in reply to MtHopper
    MtHopper said:
    I'll also need to check if the PDK we're using is compatible with IC6.1.8 (compared to IC6.1.7).

    Often foundries only specify the version they initially validated with and don't go back and keep re-validating with newer versions. However, in general it's pretty unusual for there to be a real version dependency in a PDK (it used to be more common that some PDKs did version checks, but that's much rarer nowadays). Anyway, this is part of the reason we have a new tool, PDK Cockpit, which allows you to compare behaviour of a particular PDK between two IC versions (for example).

    Regards,

    Andrew

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.