Stats

  • Locked Locked
  • Replies 8
  • Subscribers 126
  • Views 16943
  • 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

IC614 issues with $DISPLAY

tkhan

When I launch IC614 virtuoso I get the following in CIW:

 

/CMC/tools/cadence/IC-6.1.4/tools.lnx86/dfII/bin/32bit/libManager: can't open display, exiting...

/CMC/tools/cadence/IC-6.1.4/tools.lnx86/dfII/bin/32bit/libSelect: can't open display, exiting...

I can not open Library Manager or Library Path Editor as a result. As well, when I run Calibre Interactive from Virtuoso XL,  CIW shows

 \o Application initialization failed: no display name and no $DISPLAY environment variable

and Calibre does not open. IC613 and Calibre Interactive do not have this problem.

When I try getShellEnvVar("DISPLAY"), IC613 returns the correct screen, but IC614 returns nil. I have to manually do setShellEnvVar("DISPLAY=:0.0") in IC614 to resolve this issues. I am using the exact same environment setup scripts for IC613 and IC614, the sole difference being CDS_HOME for the respective IC61x installations. Any ideas?

My versions are  sub-version  IC6.1.4.500.2  (32-bit addresses) and sub-version IC6.1.3.500.16 (32-bit addresses)

Parents
  • jaro

    Hi Andrew and Tarek ... we're using a wrapper script similar to Tarek's, and found the same problem.  (Thanks to this forum, I was able to solve our problem quickly.)

    The start-up script was originally developed long ago (at least as far back as IC44 and possibly earlier) in the days when icfb and its friends accepted a command-line argument like "-display localhost:11.0".  The script, after some processing for setting up various PDKs, generated this string from the user's DISPLAY environment variable and passed it to icfb.  This was honoured (or ignored) up to version IC613, but it causes problems in IC614: the CIW and splash screens open properly, but the CIW shows errors

        {installdir}/tools.lnx86/dfII/bin/32bit/libSelect: can't open display, exiting...

        {installdir}/tools.lnx86/dfII/bin/32bit/libManager: can't open display, exiting...

    The change in behaviour was not mentioned in IC614 documentation. (It might have been mentioned in earlier releases, but I did not notice it if it was.)  Using IC613 and IC614 "virtuoso -help" does not reveal "-display" as a valid command-line switch, but neither does IC5141's "icfb -help", and it works properly there.

    Regards,

    - jaro

     p.s.No response necessary; thanks for the solution, Tarek.   -j

Reply
  • jaro

    Hi Andrew and Tarek ... we're using a wrapper script similar to Tarek's, and found the same problem.  (Thanks to this forum, I was able to solve our problem quickly.)

    The start-up script was originally developed long ago (at least as far back as IC44 and possibly earlier) in the days when icfb and its friends accepted a command-line argument like "-display localhost:11.0".  The script, after some processing for setting up various PDKs, generated this string from the user's DISPLAY environment variable and passed it to icfb.  This was honoured (or ignored) up to version IC613, but it causes problems in IC614: the CIW and splash screens open properly, but the CIW shows errors

        {installdir}/tools.lnx86/dfII/bin/32bit/libSelect: can't open display, exiting...

        {installdir}/tools.lnx86/dfII/bin/32bit/libManager: can't open display, exiting...

    The change in behaviour was not mentioned in IC614 documentation. (It might have been mentioned in earlier releases, but I did not notice it if it was.)  Using IC613 and IC614 "virtuoso -help" does not reveal "-display" as a valid command-line switch, but neither does IC5141's "icfb -help", and it works properly there.

    Regards,

    - jaro

     p.s.No response necessary; thanks for the solution, Tarek.   -j

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.