This wiki is community maintained.
For the latest departmental computing documentation, see the ITS User Guide
Cadence
From ECE Wiki
(organization) |
m (→Known Problems & Solutions) |
||
Line 1: | Line 1: | ||
==Known Problems & Solutions== | ==Known Problems & Solutions== | ||
+ | |||
+ | === '''GLIBC_2.0 not defined in file libc.so.6''' === | ||
+ | ''Affected versions: All versions bellow 5.1.14 | ||
+ | |||
+ | Affected DKs: All | ||
+ | |||
+ | Affected OS: Suse 9.3'' | ||
+ | |||
+ | Summary: When starting Cadence the following error appears | ||
+ | "/usr/cds/ic-5.0/tools/dfII/bin/icfb.exe: relocation error: /usr/cds/ic-5.0/tools/dfII/bin/icfb.exe: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference." Then Cadence software exits. This happens because older versions of Cadence don't like the new 2.6 Linux kernel. | ||
+ | Fix: Before starting Cadence software set the environment variable LD_ASSUME_KERNEL to 2.4.1. | ||
+ | If using tcsh shell, '''setenv LD_ASSUME_KERNEL 2.4.1''' | ||
+ | If using bash shell, '''LD_ASSUME_KERNEL=2.4.1""; export LD_ASSSUME_KERNEL''' | ||
+ | |||
=== '''opusdbtype''' === | === '''opusdbtype''' === | ||
''Affected versions: All | ''Affected versions: All |
Revision as of 19:50, 18 October 2005
Contents |
Known Problems & Solutions
GLIBC_2.0 not defined in file libc.so.6
Affected versions: All versions bellow 5.1.14
Affected DKs: All
Affected OS: Suse 9.3
Summary: When starting Cadence the following error appears "/usr/cds/ic-5.0/tools/dfII/bin/icfb.exe: relocation error: /usr/cds/ic-5.0/tools/dfII/bin/icfb.exe: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference." Then Cadence software exits. This happens because older versions of Cadence don't like the new 2.6 Linux kernel. Fix: Before starting Cadence software set the environment variable LD_ASSUME_KERNEL to 2.4.1.
If using tcsh shell, setenv LD_ASSUME_KERNEL 2.4.1 If using bash shell, LD_ASSUME_KERNEL=2.4.1""; export LD_ASSSUME_KERNEL
opusdbtype
Affected versions: All
Affected DKs: st065 v3.0
Affected OS: All
Summary: When starting Cadence the following error appears "Mandatory Shell Environment Variable opusdbtype is not correctly set." Then a segmentation fault. Fix: Before starting Cadence software set the environment variable opusdbtype to empty string.
If using tcsh shell, setenv opusdbtype If using bash shell, opusdbtype=""; export opusdbtype
Lost in file system
Affected Versions: All
Affected DKs: All
Affected OS: Suse 9.3
Summary: When starting Cadence, the software reports an error message "Lost in file system." The working directory is set to a junk path. Fix: Make sure the directory Cadence is being started from has list (l) permissions for system:anyuser. To do this, run this command in the directory Cadence is being started from.
fs sa . system:anyuser l