Stats

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

IC617 Running Issue at RHEL8.2

Rowshon

Hello,

First of all, I understand that RHEL 8.2 is not a supported version for IC617. But, as I already installed the Hotfix_IC06.17.722_lnx86.sdp (I haven't installed the base) and later figured out the compatibility issue, I like to see if it works before I reboot my system with other supported version of RHEL. I used Installscape for the installation and choose install from the local directory. But I got an error as it complains about the OS. I am adding snapshots of the errors I got. I would appreciate any suggestions.   

Here is a pic of my startup.ic6 file:

Thanks a lot for your time!

Parents
  • Andrew Beckett

    Well, try this follow on suggestion (and this is totally unsupported):

    export OA_UNSUPPORTED_PLAT=linux_rhel60

    (and then start virtuoso).

    If that doesn't work, try:

    export OA_UNSUPPORTED_PLAT=linux_rhel50_gcc48x

    I should reiterate that there are absolutely no guarantees doing this, and this can lead to trouble later down the line. So moving to a supported OS (and ideally supported Virtuoso version) would be advisable.

    Andrew

  • Rowshon
    in reply to Andrew Beckett

    Hi Andrew,

    Thanks a lot for the suggestion. I tried putting this line to the startup.ic6 file but I am getting a similar error. Just to make sure I'm trying things in the correct way

    1. Should I insert this line at the startup.ic6 file? If so is there any particular line I have to put it? Thinking about the order.

    2. OR this change will go to the /home/CadencE/ic6/share/oa/bin/sysname from where the error is generating?

    Thanks!  

  • Andrew Beckett
    in reply to Rowshon

    This startup.ic6 file is something to do with  your setup - it's not a standard Cadence file, but something in your environment. I would expect that you'd set this in that file and not touch the sysname program.

    If it still says "unknown", that's a bit strange, because I would expect this to be picked up in the event of an unrecognised OS. 

    However, I really would not spend too long trying to get an unsupported release running on an unsupported OS. I can't test it because I don't have access to a similar system.

    Andrew.

Reply
  • Andrew Beckett
    in reply to Rowshon

    This startup.ic6 file is something to do with  your setup - it's not a standard Cadence file, but something in your environment. I would expect that you'd set this in that file and not touch the sysname program.

    If it still says "unknown", that's a bit strange, because I would expect this to be picked up in the event of an unrecognised OS. 

    However, I really would not spend too long trying to get an unsupported release running on an unsupported OS. I can't test it because I don't have access to a similar system.

    Andrew.

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.