What's wrong with necoell? That program doesn't run and Cadence still try to sell it?

These shared libraries are all part of the NEOCELL installation. They are in <instdir>/tools/NeoCell/lib.linux in my installation.

So no wonder google didn't find them. 

Did you do the "configuration" step in InstallScape after installation? My guess is that something is wrong with your installation, or you did not launch the tool properly. You need to have <instdir>/tools/NeoCell/bin in your path, and launch the neocell from there.

Or read the documentation... (in <instdir>/tools/NeoCell/docs)

Regards,

Andrew.

In IC6.1, NeoCell is no longer a separate tool, it is integrated with Virtuoso. All the capabilities in NeoCell are now part of the Virtuoso editor with enhancements.  Be sure to contact your local Application Engineer to see this as the product you are looking at is many years out of date.

 Ted

Ok, it still complains of missing or error loading  libc.so.6: No such file or directory.

I check libc.so.6 is clearly in the system's /lib folder.                 

By "it" I assume you still mean Neocell rather than IC61. My guess is that you're trying to run Neocell on an unsupported platform (e.g. RHEL 5). The neocell wrapper script sets LD_ASSUME_KERNEL to cope with the fact that it was built with an older OS. This is fine on RHEL3 and RHEL4, but not on RHEL5 (if you check the platform support matrix for NEOCELL34, you'll see it actually only lists RedHat 7.2, RHEL3 and SLES9. Often you can get away with later OS, but in this case it would need some platform build updates to run on RHEL5.

In fact setting LD_ASSUME_KERNEL to 2.4.1 on RHEL5 breaks pretty much every application. Even "ls" does this:

andrewb_1> setenv LD_ASSUME_KERNEL 2.4.1
andrewb_2> ls
ls: error while loading shared libraries: librt.so.1: wrong ELF class: ELFCLASS32
andrewb_3> pwd
/export/home/users/andrewb
setheader: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
andrewb_4> vi
vi: error while loading shared libraries: libc.so.6: wrong ELF class: ELFCLASS32

So what OS/revision are you trying to run it on?

Regards,

Andrew.

Andrew Beckett said:

By "it" I assume you still mean Neocell rather than IC61. My guess is that you're trying to run Neocell on an unsupported platform (e.g. RHEL 5). The neocell wrapper script sets LD_ASSUME_KERNEL to cope with the fact that it was built with an older OS. This is fine on RHEL3 and RHEL4, but not on RHEL5 (if you check the platform support matrix for NEOCELL34, you'll see it actually only lists RedHat 7.2, RHEL3 and SLES9. Often you can get away with later OS, but in this case it would need some platform build updates to run on RHEL5.

In fact setting LD_ASSUME_KERNEL to 2.4.1 on RHEL5 breaks pretty much every application. Even "ls" does this:

andrewb_1> setenv LD_ASSUME_KERNEL 2.4.1
andrewb_2> ls
ls: error while loading shared libraries: librt.so.1: wrong ELF class: ELFCLASS32
andrewb_3> pwd
/export/home/users/andrewb
setheader: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
andrewb_4> vi
vi: error while loading shared libraries: libc.so.6: wrong ELF class: ELFCLASS32

So what OS/revision are you trying to run it on?

Regards,

Andrew.

I am using Redhat server enterprise 5.3 version. It's the latest.  You think the LD_ASSUME_KERNEL 2.4.1 has to do with this?

How do I fix it?

I am launching neocell from Virtuoso schematics IC5141. 

You could try using a supported platform... there's a reason why Cadence has the platform support matrix. 

Alternatively you _might_ get away with hacking the <NEOCELLinstDir>/tools/NeoCell/bin/NeoWrap script and comment out the line setting LD_ASSUME_KERNEL. I have no idea whether this will work or will break things (I'm not in the office and can't test it). If it doesn't work, you probably have no choice but to use a supported OS (I think you'd be OK with anything less than RHEL5 though - RHEL5 is too big a kernel revision change from the build platform for NEOCELL34).

The other possibility is to move to IC613 - is that a possibility? Virtuoso Layout Suite GXL provides the NeoCell functionality, but integrated into the environment.

Regards,

Andrew.

I commented out the LD_ASSUME KERNEL line, but got a different error.

tools/NeoCell/external/windu/lib.linux_i32/libwinsock50.so : symbol h_errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference.

Seems like neocell is falling apart under IC5141. 

It was a bit of a long shot to try editing the script - generally there's a good reason for LD_ASSUME_KERNEL having been used.

It's not a matter of the tool falling apart - the fundamental problem is that you're trying to run on an unsupported OS for this software.

Regards,

Andrew.

How do you access Neocell from Layout under IC610 then?

under tools?

 The NeoCell capabilities are built into Virtuoso directly at the GXL level. Go into GXL using the Launch Layout-GXL menu pick. Design constraints have to be added to the schematic and you can create modgens with your pcells and use constraint aware editing.

Ted