Assura32 problem

E

Erick

Guest
Hi All,

I just migrated the IC613 with Assura32 from school lab to my
workstation, I started assura32 from virtuoso layout XL, I found the
following errors:

Starting dfIIToVdb...
/cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: symbol lookup
error: /cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: undefined
symbol: _ZTIN12OpenAccess_424oaDesignUndoObserverBaseE
*WARNING* Translation abnormally terminated!

*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated

What are "symbol lookup error" and "undefined symbol"? What is
"_ZTIN12OpenAccess_424oaDesignUndoObserverBaseE"?
How to deal with this problem?

Thanks,
Erick
 
Erick wrote, on 09/01/09 00:31:
Hi All,

I just migrated the IC613 with Assura32 from school lab to my
workstation, I started assura32 from virtuoso layout XL, I found the
following errors:

Starting dfIIToVdb...
/cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: symbol lookup
error: /cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: undefined
symbol: _ZTIN12OpenAccess_424oaDesignUndoObserverBaseE
*WARNING* Translation abnormally terminated!

*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated

What are "symbol lookup error" and "undefined symbol"? What is
"_ZTIN12OpenAccess_424oaDesignUndoObserverBaseE"?
How to deal with this problem?

Thanks,
Erick
Do you have $OAHOME defined before starting virtuoso? If so, you will want to
unset it. In csh this is "unsetenv OAHOME"; in sh/ksh/bash it is "unset OAHOME".

Check both your IC613 and Assura32 installation directories to ensure they both
have a share/oa directory (this is most likely a link) - linking to the
OpenAccess installation that came with each release. Perhaps you can show what:

cd <IC613instDir>
cd share
ls -l

cd <Assura32InstDir>
cd share
ls -l

gives?

Regards,

Andrew.
 
Andrew Beckett wrote, on 09/01/09 09:57:
Erick wrote, on 09/01/09 00:31:
Hi All,

I just migrated the IC613 with Assura32 from school lab to my
workstation, I started assura32 from virtuoso layout XL, I found the
following errors:

Starting dfIIToVdb...
/cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: symbol lookup
error: /cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: undefined
symbol: _ZTIN12OpenAccess_424oaDesignUndoObserverBaseE
*WARNING* Translation abnormally terminated!

*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated

What are "symbol lookup error" and "undefined symbol"? What is
"_ZTIN12OpenAccess_424oaDesignUndoObserverBaseE"?
How to deal with this problem?

Thanks,
Erick

Do you have $OAHOME defined before starting virtuoso? If so, you will
want to unset it. In csh this is "unsetenv OAHOME"; in sh/ksh/bash it is
"unset OAHOME".

Check both your IC613 and Assura32 installation directories to ensure
they both have a share/oa directory (this is most likely a link) -
linking to the OpenAccess installation that came with each release.
Perhaps you can show what:

cd <IC613instDir
cd share
ls -l

cd <Assura32InstDir
cd share
ls -l

gives?

Regards,

Andrew.
Apologies for the typo - the environment variable to check for is $OA_HOME not
$OAHOME ...

Regards,

Andrew.
 
On Sep 1, 8:17 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm>
wrote:
Andrew Beckett wrote, on 09/01/09 09:57:



Erick wrote, on 09/01/09 00:31:
Hi All,

I just migrated the IC613 with Assura32 from school lab to my
workstation,  I started assura32 from virtuoso layout XL,  I found the
following errors:

Starting dfIIToVdb...
/cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: symbol lookup
error: /cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: undefined
symbol: _ZTIN12OpenAccess_424oaDesignUndoObserverBaseE
*WARNING* Translation abnormally terminated!

*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated

What are "symbol lookup error" and "undefined symbol"?  What is
"_ZTIN12OpenAccess_424oaDesignUndoObserverBaseE"?
How to deal with this problem?

Thanks,
Erick

Do you have $OAHOME defined before starting virtuoso? If so, you will
want to unset it. In csh this is "unsetenv OAHOME"; in sh/ksh/bash it is
"unset OAHOME".

Check both your IC613 and Assura32 installation directories to ensure
they both have a share/oa directory (this is most likely a link) -
linking to the OpenAccess installation that came with each release.
Perhaps you can show what:

cd <IC613instDir
cd share
ls -l

cd <Assura32InstDir
cd share
ls -l

gives?

Regards,

Andrew.

Apologies for the typo - the environment variable to check for is $OA_HOME not
$OAHOME ...

Regards,

Andrew.
Hi Andy,

Thanks for your valuable help, following to your step, the problems
are fixed.

Thanks!

Erick
 
On Sep 1, 8:17 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm>
wrote:
Andrew Beckett wrote, on 09/01/09 09:57:



Erick wrote, on 09/01/09 00:31:
Hi All,

I just migrated the IC613 with Assura32 from school lab to my
workstation,  I started assura32 from virtuoso layout XL,  I found the
following errors:

Starting dfIIToVdb...
/cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: symbol lookup
error: /cadence/assura32/tools/assura/bin/32bit/dfIIToVdb: undefined
symbol: _ZTIN12OpenAccess_424oaDesignUndoObserverBaseE
*WARNING* Translation abnormally terminated!

*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated

What are "symbol lookup error" and "undefined symbol"?  What is
"_ZTIN12OpenAccess_424oaDesignUndoObserverBaseE"?
How to deal with this problem?

Thanks,
Erick

Do you have $OAHOME defined before starting virtuoso? If so, you will
want to unset it. In csh this is "unsetenv OAHOME"; in sh/ksh/bash it is
"unset OAHOME".

Check both your IC613 and Assura32 installation directories to ensure
they both have a share/oa directory (this is most likely a link) -
linking to the OpenAccess installation that came with each release.
Perhaps you can show what:

cd <IC613instDir
cd share
ls -l

cd <Assura32InstDir
cd share
ls -l

gives?

Regards,

Andrew.

Apologies for the typo - the environment variable to check for is $OA_HOME not
$OAHOME ...

Regards,

Andrew.
Hi Andy,

Thanks for your valuable help, following to your step, the problems
are fixed.

Thanks!

Erick
 

Welcome to EDABoard.com

Sponsor

Back
Top