I just installed IC610 on our Linux machine (radhat enterprise5, 64bit) . We have a IC5141 on it already by the way. I got error when I tried to run the IC610. I put "virtuoso" and error information comes:
/cadence/IC610/tools/dfII/32bit/virtuoso: symbol lookup error: /cadence/IC610/tools/QT/lib/libQTGui.so.4: undefined symbol: XRenderFindStandardFormat
Does anyone know how to solve this?
Thanks a lot!
Not seen this reported before, but it appears to come from /usr/lib/libXrender.so.1 - which is provided via the:
UNIX> rpm -q -f /usr/lib/libXrender.so.1libXrender-0.9.1-3.1.i386
rpm. There's a similar 64 bit version as well. Of course, the exact version may depend on your OS.
Maybe you don't have it installed, or have an old version? Is it reallyy IC610? Or is it IC614 or IC615 that you're installing (IC614 is shown under IC610 in downloads.cadence.com since it's an update release of IC610, although in practice it is very different - I would strongly recommend against using the IC610 base release these days, since that came out 4.5 years ago and there have been major updates since then).
In reply to Andrew Beckett:
Hi Andrew,Thanks for the reply.The version we installed is IC610. We didn't select IC614 or any other updates when we installed it, just IC610 base.I found the 'usr/lib/libXrender.so.1' file, but didn't see file "libXrender-0.9.1-3.1.i386" you mentioned. Do you know how to check if I have the right "libXrender.so.1" file? and how about the "libXrender-0.9.1-3.1.i386" file? is it in the same folder or somewhere else?Thank you so much for the help.
In reply to Sindy:
Unfortunately I cannot work out why this is failing - the version of the RPM looks OK, and I've tried running the base IC610 on a machine with a similar RPM (even with CDS_AUTO_64BIT set to ALL), and similar Assura and MMSIM versions - I cannot get it to fail.
Do you have $LD_ASSUME_KERNEL set? What OS are you running on (what does "cat /etc/redhat-release" show and what does "uname -a" show)?
Either way, this version is not supported any longer, so you really would be far better off installing either IC614 or IC615.
[LuLi@ee207 ~]$ uname -aLinux ee207.dhcp.ttu.edu 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14 EST 2007 x86_64 x86_64 x86_64 GNU/Linux[LuLi@ee207 ~]$ cat /etc/redhat-releaseRed Hat Enterprise Linux Client release 5 (Tikanga)
About the "$LD_ASSUME_KERNEL set", I don't know how to check it.. Sorry. Could you let me know how to?
If we cannot figure this out, we will switch to IC614 or IC615 as you suggest.
I updated our IC610 to IC614. But we had failures. The failure information is as following:
Error Downloading file:http://software.cadence.com/is/IC610/lnx86/Hotfix_IC06.14.511-614/Hotfix_IC06.14.511-614_lnx86.sdp
Error Downloading file:http://software.cadence.com/is/IC610/lnx86/Hotfix_IC06.14.511-614/CDROM1/README
When we tried to run it after the install (Something wasn't installed due to the downloading error, but we run it anyway), there are error information as following:
/cadence/IC610/tools/dfII/bin/64bit/virtuoso:error while loading shared libraries: liboaCM. so: cannot open shared object file: no such file or directory
I'm not sure if this error is due to the downloading and install failure. Do you have any advices?
If you had failures during the download and install, why do you assume that the software will be able to work after knowing that it did not complete the installation task successfully? I would recommend repeating the installation to completion and then seeing if you have issues after that; it seems the logical course of action to me.
In reply to skillUser:
Yes. You are right. I just successfully installed the missing files.
But still we have the error when run it.
/cadence/IC610/tools/dfII/bin/64bit/virtuoso:error while loading shared
libraries: liboaCM. so: cannot open shared object file: no such file or
Any clue? am I missing some shared library file? or a symbolic link missed?
Thanks you Lawrence
Do you have $OA_HOME set? If so, please unset the environment variable (in csh "unsetenv OA_HOME"). Did you do the configuration step after installing IC614, and if so, did you tell it to use the OpenAccess installation from somewhere else? The best thing to do is not to configure OpenAccess - leave it at the default which is to point at the OA build that comes with IC614. For example, at the root of your installation (/cadence/IC610 in your case) I have:
andrewb_26> ls -l share/oalrwxrwxrwx 1 eucdsmgr mail 16 Feb 13 00:09 share/oa -> ../oa_v22.04.072/
If you look in share/oa/lib/*/opt you should see the file that it's complaining about.
My guess is that either OA_HOME has been set, or your share/oa link is pointing in the wrong place.
My OA setup situlation is: I configured OpenAccess after I installed IC610 base (directory: /cadence/IC610/OA), but I didn't change the OA configuration after I updating to 614 (When I did the configuration after updating, I jumped the OA part).Now there is another OA profile: /cadence/IC610/oa_v22.04.072, which I believe comes with the IC614.
NOt sure if I have $OA_HOME set. What I did was set OA_HOME in the "bash" file (export OA_HOME=/cadence/IC610/OA).
Besides, could you please let me know how to "unset the envionment variable (in csh "unsetenv OA_HOME")?" what do you mean by "csh"? Sorry I'm a rookie.
Please remove the definition of OA_HOME from your .bashrc (if that's where you put it). Interactively (in the bash shell) you can always type "unset OA_HOME" (unsetenv is the equivalent csh (C shell, an alternative to "bash" or "ksh" or the various other shells in UNIX) syntax, but since you're not using csh it's irrelevant). Setting OA_HOME is not a good idea for any of the Cadence releases; they should always use the OpenAccess libraries that come with the tools, as that is what they were tested with. It certainly will not work to use IC614 with the OA libraries from IC610 - they aren't even the same data model.
Having done this, can you check that /cadence/IC610/share/oa is a link to the oa_v22.04.072 directory (do an "ls -l /cadence/IC610/share/" to check).
I unset the OA_HOME, then I got another error
/cadence/IC610/tools/dfII/bin/64bit/virtuoso: error while loading shared libraries: libQtAssistantClient.so.4: cannot open shared object file: No such file or directory
If I further remove "export CDS_AUTO_64BIT=ALL" in the bash file, the error information goes back to our very first one with IC610.
/cadence/IC610/tools/dfII/32bit/virtuoso: symbol lookup error:
/cadence/IC610/tools/QT/lib/libQTGui.so.4: undefined symbol:
I guess I should keep the "export CDS_AUTO_64BIT=ALL" since our machine is 64 bit, right?
THe result of "ls -l /cadence/IC610/share/" is:
total 172drwxr-xr-x 2 cdsmgr cdsmgr 4096 Feb 4 03:33 bindrwxr-xr-x 7 cdsmgr cdsmgr 4096 Oct 22 11:45 catenadrwxrwxr-x 3 cdsmgr cdsmgr 4096 Apr 8 15:42 cdsdocdrwxr-xr-x 19 cdsmgr cdsmgr 4096 Feb 4 03:33 cdssetupdrwxr-xr-x 3 cdsmgr cdsmgr 4096 Nov 10 15:44 csr_ccodrwxr-xr-x 3 cdsmgr cdsmgr 4096 Jan 10 05:23 deftdrwxr-xr-x 3 cdsmgr cdsmgr 4096 Feb 4 03:33 dfIIdrwxr-xr-x 2 cdsmgr cdsmgr 4096 Oct 11 2006 gpdkdrwxr-xr-x 2 cdsmgr cdsmgr 4096 Aug 25 2009 ildrwxr-xr-x 3 cdsmgr cdsmgr 4096 Jan 6 22:24 iotadrwxr-xr-x 5 cdsmgr cdsmgr 4096 Feb 4 03:45 javadrwxr-xr-x 2 cdsmgr cdsmgr 4096 Oct 11 2007 licenselrwxrwxrwx 1 cdsmgr cdsmgr 16 Apr 11 18:56 oa -> ../oa_v22.04.072drwxr-xr-x 2 cdsmgr cdsmgr 4096 Jan 4 04:14 oaInstallersdrwxr-xr-x 2 cdsmgr cdsmgr 4096 Jan 3 20:14 oaPlugInsdrwxr-xr-x 5 cdsmgr cdsmgr 4096 Nov 6 2009 patchDatadrwxr-xr-x 3 cdsmgr cdsmgr 4096 Jan 7 2005 sevdrwxrwxr-x 3 cdsmgr cdsmgr 4096 Oct 25 2006 snadrwxr-xr-x 2 cdsmgr cdsmgr 4096 Aug 25 2009 tcldrwxr-xr-x 3 cdsmgr cdsmgr 4096 Apr 15 2010 tlfUtildrwxrwxr-x 4 cdsmgr cdsmgr 4096 May 19 2006 veritydrwxr-xr-x 2 cdsmgr cdsmgr 4096 Jan 4 04:14 version
Just because you're running on a 64 bit machine doesn't mean you have to run the 64-bit versions of the executables. The 32 bit versions will run perfectly well on 64 bit hardware (in fact there's a small performance penalty with running the 64-bit versions, because the memory usage is greater as all pointers become 8 bytes rather than 4 bytes, so the memory access takes longer). So you only need to use 64 bit mode if your designs have capacity limitations (i.e. the executable needs more than about 3.7Gbytes of memory).
The error about libQtAssistantClient.so.4 is very odd - this should be found in the tools/QT/lib/64bit dir in the installation (and also in the tools/QT/lib dir for 32 bit).
Something sounds very wrong here. You seem to be getting very peculiar failures which do not match what we've seen anywhere else.
You should contact Customer Support (or contact Cadence through your normal support channel if you're a university) - as it's going to be very hard to diagnose this in a community forum.
Thanks for the advices. We'll turn to them and see what they can do.
Thanks for all the help.