• 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. Assura RCX fails

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 127
  • Views 19319
  • 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

Assura RCX fails

pitter
pitter over 15 years ago

Hi!

 When running RCX extraction with RC option (there is no error when Only C extraction is performed)I get the following error:

/home/piter/Cadence/Assura/tools.lnx86/assura/bin/32bit/labprint: relocation error: /home/piter/Cadence/Assura/tools.lnx86/assura/bin/32bit/labprint: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
*ERROR* at "connect": /home/piter/Cadence/Assura/tools.lnx86/assura/bin/32bit/labprint failed with status 127
*WARNING* Bad return status from RCX run. 0x100

 Thanks in advance for any help,

 pitter.

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

    Hi pitter,

    It generally helps when talking about problems such as this to know which Assura version you're using (type "assura -W") and which OS release you're using (for example "cat /etc/redhat-release").

    This looks like a problem in ASSURA317 and ASSURA32 when running on RHEL5. The CCR I found on this said it was fixed in ASSURA41 (make sure you get the most recent version); I believe it may also be solved if you use QRC (the EXT81 or EXT91 streams) for extraction; Assura RCX is effectively end-of-lifed and replaced by QRC from the EXT stream (it's compatible technology).

    But this is all a bit of a guess since you didn't say what software version or OS version you're using.

    Best Regards,

    Andrew.

     

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

    Hi pitter,

    It generally helps when talking about problems such as this to know which Assura version you're using (type "assura -W") and which OS release you're using (for example "cat /etc/redhat-release").

    This looks like a problem in ASSURA317 and ASSURA32 when running on RHEL5. The CCR I found on this said it was fixed in ASSURA41 (make sure you get the most recent version); I believe it may also be solved if you use QRC (the EXT81 or EXT91 streams) for extraction; Assura RCX is effectively end-of-lifed and replaced by QRC from the EXT stream (it's compatible technology).

    But this is all a bit of a guess since you didn't say what software version or OS version you're using.

    Best 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