dvelasco
Newbie level 3
kde crashes cadence
Hello Everybody, this is my first post in elektroda.pl.
Im the system manager at my work, and we are testing all the newest cadence software in Fedora Core 1. We are using it because we have find it is better using system resources than redhat 7.3
We are in close contact with cadence, and the have said specifically they only support redhat 7.3 and in a future, redhat enterprise 2, and maybe for next year, version 3. This is because they need an stable system to run on.
I'm posting what we have found fiddling about with the following unsupported configurations:
1) Fedora Core 1 fresh install, ic5032, assura3_1
2) Fedora Core 1 apt-get updated version (freshrpms.net), ic5032, assura3_1
3) Fedora Core 1 fresh install, ic5033, assura3_1
4) Fedora Core 1 apt-get update, ic5033, assura3_1
5) Same as 4, using kde3.2beta2
6) Same as 5, using kernel 2.6.1
The results were
1) Doesn't work. There has been a major change in Fedora's glibc.
You can activate a compatibility mode workaround by defining
LD_ASSUME_KERNEL 2.4.19 (not 2.2.5 because cadence compiles for 2.4.17 and further)
With this change, ICFB is ok, library manager and almost all basic functions works. Hierarchy Editor is broken. Virtuoso Schematic was fully functional. Virtuoso Layout and XL extension are broken when generating from a source schematic. Spectre DOES NOT work. Maybe there are some more errors around. Assura seems runs ok.
2) Same as 1.
3) Virtuoso Layout is fully functional. XL is a bit buggy and tends to close when moving instances.
4) Same as 3
5) kde32beta2 is usable, but has many stupid bugs which can make you destroy your cadence windows, and thus, should be avoided.
6) Armageddon!!!! ICFB gets completely broken, can't connect to Library Manager. I tested Library Manager by itself but cannot interconnect to virtuoso or other programs. We wouldn't recommend moving to kernel 2.6 until finding what's failing and finding a workaround.
Also, we have tested iccraft, and it works ok, except for a bug when trying to configure bind keys.
Also, a pre-patch for assura3_1 made it crash in fedora, but is usable in redhat 7.3
Also, we are trying to deprecate the use of the .cshrc configuration of cadence, instead, we have made a kde-linked script to configure everything. The script is very preliminar, and it's going to include license servers verification, and a full configuration system.
Well people, I hope this information is useful for anyone.
Hello Everybody, this is my first post in elektroda.pl.
Im the system manager at my work, and we are testing all the newest cadence software in Fedora Core 1. We are using it because we have find it is better using system resources than redhat 7.3
We are in close contact with cadence, and the have said specifically they only support redhat 7.3 and in a future, redhat enterprise 2, and maybe for next year, version 3. This is because they need an stable system to run on.
I'm posting what we have found fiddling about with the following unsupported configurations:
1) Fedora Core 1 fresh install, ic5032, assura3_1
2) Fedora Core 1 apt-get updated version (freshrpms.net), ic5032, assura3_1
3) Fedora Core 1 fresh install, ic5033, assura3_1
4) Fedora Core 1 apt-get update, ic5033, assura3_1
5) Same as 4, using kde3.2beta2
6) Same as 5, using kernel 2.6.1
The results were
1) Doesn't work. There has been a major change in Fedora's glibc.
You can activate a compatibility mode workaround by defining
LD_ASSUME_KERNEL 2.4.19 (not 2.2.5 because cadence compiles for 2.4.17 and further)
With this change, ICFB is ok, library manager and almost all basic functions works. Hierarchy Editor is broken. Virtuoso Schematic was fully functional. Virtuoso Layout and XL extension are broken when generating from a source schematic. Spectre DOES NOT work. Maybe there are some more errors around. Assura seems runs ok.
2) Same as 1.
3) Virtuoso Layout is fully functional. XL is a bit buggy and tends to close when moving instances.
4) Same as 3
5) kde32beta2 is usable, but has many stupid bugs which can make you destroy your cadence windows, and thus, should be avoided.
6) Armageddon!!!! ICFB gets completely broken, can't connect to Library Manager. I tested Library Manager by itself but cannot interconnect to virtuoso or other programs. We wouldn't recommend moving to kernel 2.6 until finding what's failing and finding a workaround.
Also, we have tested iccraft, and it works ok, except for a bug when trying to configure bind keys.
Also, a pre-patch for assura3_1 made it crash in fedora, but is usable in redhat 7.3
Also, we are trying to deprecate the use of the .cshrc configuration of cadence, instead, we have made a kde-linked script to configure everything. The script is very preliminar, and it's going to include license servers verification, and a full configuration system.
Well people, I hope this information is useful for anyone.
