• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. What's wrong with necoell? That program doesn't run and...

Stats

  • Locked Locked
  • Replies 14
  • Subscribers 126
  • Views 5382
  • 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

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

archive
archive over 16 years ago

Try to try out the program if it's any good.  ./neocell   it would complains missing library of libsstring.so,  libechelon.so, libwmb.so , what?

Those library names aren't even in Redhat enterprise 5.3 disk..  Do a google search,  no such libraries found either.

obviously, that program is not working and probably nobody ever buy it.  Otherwise how can people not complain about missing some exotic named libraries that can't even found in google. 

 

 

 

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 16 years ago

    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.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 16 years ago

    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.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information