• 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. RF Design
  3. *WARNING* QRC_HOME environmental variable is set but UI...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 63
  • Views 2429
  • 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

*WARNING* QRC_HOME environmental variable is set but UI can't locate correct QRC installation

Aldo2
Aldo2 over 13 years ago

 Hello,

I get the following warning with QRC:

 *WARNING* QRC_HOME environmental variable is set but UI can't locate correct QRC installation.
          In order to run UI in QRC compatibility mode you need to have QRC executables in your $PATH and QRC version should be 8.1 or greater.
          Check your QRC installation and environmental settings.

I am using:

ic 615isr20120513 and pve 1111isr20120629

Thank you very much

Best Regards

Aldo

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Aldo,

    The only way I can get this to happen is if I have QRC_HOME set to <PVEinstallationDir> but not having <PVEinstallationDir>/bin in my PATH. So can you check $QRC_HOME and $PATH to ensure they are correct?

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Aldo2
    Aldo2 over 13 years ago

    Hi Andrew,

    I have found the error! It is not explained on CIW (only the message I wrote previously is shown on CIW), but in the pvsUI_ipvs.log file, created in the directory on which I run virtuoso.

    The error was caused by a missing library (GLIB_2.4) in the server I was using for my simulations.

    I'm wondering why the same message is not shown on CIW or why is not shown a message telling the user to open this file.

    Thank you

    Best Regards,

    Aldo

     

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

    Aldo,

    I agree, reporting every possible error in a way that is clear to the user is important - but sometimes it's hard to anticipate every possible error - and some things get missed when designing the software and testing it.

    Regards,

    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