Stats

  • Locked Locked
  • Replies 2
  • Subscribers 129
  • Views 15410
  • 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

avlck does not return the correct name from sysname

bpdegnan
 I have something strange happening where avlck is not receiving the correct value from sysname, which is returning unknown.  This occurs when I use Assura to LVS.  Assura works fine for DRC.
 
localhost:~/ic/cadence/ibm7sf> avlck:   ERROR: The command /tools/cadence/assura615oa/share/oa/bin/sysname returned an error status:
                            unknown
avlck:    INFO: Note that OpenAccess (OA) requires running the Configure phase.
avlck:          See the "OpenAccess Installation and Configuration Guide" before
avlck:          you complete the configuration step. This manual is included with
avlck:          the Cadence product documentation.

localhost:~/ic/cadence/ibm7sf>  /tools/cadence/assura615oa/share/oa/bin/sysname
linux_rhel40_gcc44x
 
So, the question comes down to why "avlck" is not getting the same thing back as sysname.  Is there someway to force the return value so that Assura works?   I'm moving my work from IC5 to IC6, and this has been my only hickup so far.
 
Any ideas would be greatly appreciated.
 
Cheers,
Brian Degnan, Ph.D. 
  • Andrew Beckett

    It sounds as if you might be running on an OS that wasn't (or isn't) supported, although it is a bit odd that sysname works from the command line. What distribution are you using? If it is RedHat what does "cat /etc/redhat-release" show? On SuSE I think it is suse-release from the top of my head.

    Also, what subversion of ASSURA are you using (type "assura -W")

    Thanks,

    Andrew

  • bpdegnan

    I solved the issue after scratching my head for a day.  It's amazing what time away from a problem will do. The short answer to the issue was to add LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:$ASSURAHOME/tools/lib" to my shell.

    There was an error where I was not including the library path specifically for the assura libraries. Assura mostly worked because it was finding other libraries that are used in IC6. I discovered this by running what Assura actually runs:

    localhost:~/ic/cadence/ibm7sf> sh ./.assura_LVS.run
    This resulted in an interesting error:
    /tools/cadence/assura615oa/tools/assura/bin/32bit/assura: error while loading shared libraries: libgfortran.so.3: wrong ELF class: ELFCLASS64
    The next thing that I did was run LDD to find what was missing, and I've attached a subset of the output below.
    ldd /tools/cadence/assura615oa/tools/assura/bin/32bit/assura
        libpthread.so.0 => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xf76d5000)
        libgfortran.so.3 => not found
        librt.so.1 => /lib/i386-linux-gnu/i686/cmov/librt.so.1 (0xf76cc000)

    libgfortran.so.3 exists in my $ASSURAHOME/tools/lib directory, so it then occured to me that our setup scripts might be missing a library entry. Adding LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:$ASSURAHOME/tools/lib" to my shell fixed the issue.  

    All-in-all, this tops my list of all-time strange errors, but at least now it's documented.  

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.