ISU55 vhdl error

T

tritue

Guest
We have a VHDL design using LDV51 and it work well. We just change to IUS55
and each time we compile
ncvhdl we have following message

ncvhdl_p: *F,DLUNNE: Can't find STANDARD at
/software/linux/ius55/tools/inca/files/STD

we compile the STD package using the cadence install script and it report
no error.

If I use ncvhdl in IUS55 with library from ldv51, it will report same
messages

Any idea where I have to look.
 
On Wed, 4 Jan 2006 14:45:16 -0500, "tritue" <ttt@yahoo.com> wrote:

We have a VHDL design using LDV51 and it work well. We just change to IUS55
and each time we compile
ncvhdl we have following message

ncvhdl_p: *F,DLUNNE: Can't find STANDARD at
/software/linux/ius55/tools/inca/files/STD

we compile the STD package using the cadence install script and it report
no error.

If I use ncvhdl in IUS55 with library from ldv51, it will report same
messages

Any idea where I have to look.
Try the following:

cd /software/linux/ius55/tools/inca/files/STD

andrewb_6> ls STD
inca.lnx86.157.pak inca.lnx8664.157.pak standard/ textio/
andrewb_7> ncls -lib STD
ncls: *E,NOROPN: cannot open logfile 'ncls.log'.
ncls: 05.50-s009: (c) Copyright 1995-2005 Cadence Design Systems, Inc.
package STD.STANDARD (AST)
package STD.STANDARD (COD) <0x7a2c0eaf>
package STD.STANDARD (COD) <0x7a2c0eb0>
package STD.STANDARD (COD) <0x7a2c0eb1>
package STD.STANDARD (COD) <0x7a2c0eb3>
package STD.STANDARD (COD) <0x7a2c0eb4>
package STD.STANDARD (COD) <0x7a2c0eb5>
package STD.STANDARD (COD) <0x7a2c0eb6>
package STD.STANDARD (COD) <0x7a2c0eb7>
package STD.STANDARD (COD) <0x7a2c8b7a>
package STD.TEXTIO (AST)
package STD.TEXTIO (COD) <0x7a2c0eaf>
package STD.TEXTIO (COD) <0x7a2c0eb0>
package STD.TEXTIO (COD) <0x7a2c0eb1>
package STD.TEXTIO (COD) <0x7a2c0eb3>
package STD.TEXTIO (COD) <0x7a2c0eb4>
package STD.TEXTIO (COD) <0x7a2c0eb5>
package STD.TEXTIO (COD) <0x7a2c0eb6>
package STD.TEXTIO (COD) <0x7a2c0eb7>
package STD.TEXTIO (COD) <0x7a2c8b7a>
package body STD.TEXTIO:BODY (AST)
package body STD.TEXTIO:BODY (COD) <0x7a2c0eaf>
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb0>
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb1>
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb3>
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb4>
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb5>
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb6>
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb7>
package body STD.TEXTIO:BODY (COD) <0x7a2c8b7a>

If you're not getting something similar to the above, then it hasn't been
compiled as you think... you should do the configuration step in
softload/installscape (depending on how you installed the software).

Check also (cd to a writable area first) what:

ncsuffix -pak

gives - if it matches the pak files in the STD dir (assuming there are any).

Regards,

Andrew.
 
We have two machines with REL4 x86 and x8664 respectively
In the x86 machine It work well in the lnx86 machine but does not work in
the x8664 machine as show:

what should I do ??
Thank you

1) ln86 machine
ncsuffix -pak
ncsuffix: 05.50-s009: (c) Copyright 1995-2005 Cadence Design Systems, Inc.
lnx86.157.pak

ncls -package *
ncls: 05.50-s009: (c) Copyright 1995-2005 Cadence Design Systems, Inc.
ncls: *W,NOMTCH: No matching object found for 'STANDARD'.
ncls: *W,NOMTCH: No matching object found for 'inca.lnx86.151.pak'.
ncls: *W,NOMTCH: No matching object found for 'inca.lnx86.157.pak'.
ncls: *W,NOMTCH: No matching object found for 'inca.lnx8664.157.pak'.
ncls: *W,NOMTCH: No matching object found for 'ncls.log'.
ncls: *W,NOMTCH: No matching object found for 'ncsuffix.log'.
package STD.STANDARD (AST)
package STD.STANDARD (COD) <0x7a2c0eb7>
package STD.TEXTIO (AST)
package STD.TEXTIO (COD) <0x7a2c0eb7>

2) ln8664 machine

ncsuffix -pak
ncsuffix(64): 05.50-s009: (c) Copyright 1995-2005 Cadence Design Systems,
Inc.
lnx8664.157.pak
ls
STANDARD inca.lnx86.157.pak ncls.log standard
inca.lnx86.151.pak inca.lnx8664.157.pak ncsuffix.log textio
ncls -package *
ncls(64): 05.50-s009: (c) Copyright 1995-2005 Cadence Design Systems, Inc.
ncls: *W,NOMTCH: No matching object found for 'STANDARD'.
ncls: *W,NOMTCH: No matching object found for 'inca.lnx86.151.pak'.
ncls: *W,NOMTCH: No matching object found for 'inca.lnx86.157.pak'.
ncls: *W,NOMTCH: No matching object found for 'inca.lnx8664.157.pak'.
ncls: *W,NOMTCH: No matching object found for 'ncls.log'.
ncls: *W,NOMTCH: No matching object found for 'ncsuffix.log'.
ncls: *W,NOMTCH: No matching object found for 'standard'.
ncls: *W,NOMTCH: No matching object found for 'textio'.

"Andrew Beckett" <andrewb@DcEaLdEeTnEcTe.HcIoSm> wrote in message
news:lffpr1d9fqjqpdcpkqhfd0kj2ijj5de4u6@4ax.com...
On Wed, 4 Jan 2006 14:45:16 -0500, "tritue" <ttt@yahoo.com> wrote:

We have a VHDL design using LDV51 and it work well. We just change to
IUS55
and each time we compile
ncvhdl we have following message

ncvhdl_p: *F,DLUNNE: Can't find STANDARD at
/software/linux/ius55/tools/inca/files/STD

we compile the STD package using the cadence install script and it report
no error.

If I use ncvhdl in IUS55 with library from ldv51, it will report same
messages

Any idea where I have to look.



Try the following:

cd /software/linux/ius55/tools/inca/files/STD

andrewb_6> ls STD
inca.lnx86.157.pak inca.lnx8664.157.pak standard/ textio/
andrewb_7> ncls -lib STD
ncls: *E,NOROPN: cannot open logfile 'ncls.log'.
ncls: 05.50-s009: (c) Copyright 1995-2005 Cadence Design Systems, Inc.
package STD.STANDARD (AST)
package STD.STANDARD (COD) <0x7a2c0eaf
package STD.STANDARD (COD) <0x7a2c0eb0
package STD.STANDARD (COD) <0x7a2c0eb1
package STD.STANDARD (COD) <0x7a2c0eb3
package STD.STANDARD (COD) <0x7a2c0eb4
package STD.STANDARD (COD) <0x7a2c0eb5
package STD.STANDARD (COD) <0x7a2c0eb6
package STD.STANDARD (COD) <0x7a2c0eb7
package STD.STANDARD (COD) <0x7a2c8b7a
package STD.TEXTIO (AST)
package STD.TEXTIO (COD) <0x7a2c0eaf
package STD.TEXTIO (COD) <0x7a2c0eb0
package STD.TEXTIO (COD) <0x7a2c0eb1
package STD.TEXTIO (COD) <0x7a2c0eb3
package STD.TEXTIO (COD) <0x7a2c0eb4
package STD.TEXTIO (COD) <0x7a2c0eb5
package STD.TEXTIO (COD) <0x7a2c0eb6
package STD.TEXTIO (COD) <0x7a2c0eb7
package STD.TEXTIO (COD) <0x7a2c8b7a
package body STD.TEXTIO:BODY (AST)
package body STD.TEXTIO:BODY (COD) <0x7a2c0eaf
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb0
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb1
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb3
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb4
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb5
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb6
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb7
package body STD.TEXTIO:BODY (COD) <0x7a2c8b7a

If you're not getting something similar to the above, then it hasn't been
compiled as you think... you should do the configuration step in
softload/installscape (depending on how you installed the software).

Check also (cd to a writable area first) what:

ncsuffix -pak

gives - if it matches the pak files in the STD dir (assuming there are
any).

Regards,

Andrew.
 
I found the error
We should run the install script for the x86 machine in a x86 machine
(ncvhdl.ins) and then
run the installation script for the x86-64 on a x86_64 machine
(ncvhdl64b.ins).

thank for your help

"Andrew Beckett" <andrewb@DcEaLdEeTnEcTe.HcIoSm> wrote in message
news:lffpr1d9fqjqpdcpkqhfd0kj2ijj5de4u6@4ax.com...
On Wed, 4 Jan 2006 14:45:16 -0500, "tritue" <ttt@yahoo.com> wrote:

We have a VHDL design using LDV51 and it work well. We just change to
IUS55
and each time we compile
ncvhdl we have following message

ncvhdl_p: *F,DLUNNE: Can't find STANDARD at
/software/linux/ius55/tools/inca/files/STD

we compile the STD package using the cadence install script and it report
no error.

If I use ncvhdl in IUS55 with library from ldv51, it will report same
messages

Any idea where I have to look.



Try the following:

cd /software/linux/ius55/tools/inca/files/STD

andrewb_6> ls STD
inca.lnx86.157.pak inca.lnx8664.157.pak standard/ textio/
andrewb_7> ncls -lib STD
ncls: *E,NOROPN: cannot open logfile 'ncls.log'.
ncls: 05.50-s009: (c) Copyright 1995-2005 Cadence Design Systems, Inc.
package STD.STANDARD (AST)
package STD.STANDARD (COD) <0x7a2c0eaf
package STD.STANDARD (COD) <0x7a2c0eb0
package STD.STANDARD (COD) <0x7a2c0eb1
package STD.STANDARD (COD) <0x7a2c0eb3
package STD.STANDARD (COD) <0x7a2c0eb4
package STD.STANDARD (COD) <0x7a2c0eb5
package STD.STANDARD (COD) <0x7a2c0eb6
package STD.STANDARD (COD) <0x7a2c0eb7
package STD.STANDARD (COD) <0x7a2c8b7a
package STD.TEXTIO (AST)
package STD.TEXTIO (COD) <0x7a2c0eaf
package STD.TEXTIO (COD) <0x7a2c0eb0
package STD.TEXTIO (COD) <0x7a2c0eb1
package STD.TEXTIO (COD) <0x7a2c0eb3
package STD.TEXTIO (COD) <0x7a2c0eb4
package STD.TEXTIO (COD) <0x7a2c0eb5
package STD.TEXTIO (COD) <0x7a2c0eb6
package STD.TEXTIO (COD) <0x7a2c0eb7
package STD.TEXTIO (COD) <0x7a2c8b7a
package body STD.TEXTIO:BODY (AST)
package body STD.TEXTIO:BODY (COD) <0x7a2c0eaf
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb0
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb1
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb3
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb4
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb5
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb6
package body STD.TEXTIO:BODY (COD) <0x7a2c0eb7
package body STD.TEXTIO:BODY (COD) <0x7a2c8b7a

If you're not getting something similar to the above, then it hasn't been
compiled as you think... you should do the configuration step in
softload/installscape (depending on how you installed the software).

Check also (cd to a writable area first) what:

ncsuffix -pak

gives - if it matches the pak files in the STD dir (assuming there are
any).

Regards,

Andrew.
 

Welcome to EDABoard.com

Sponsor

Back
Top