beautypg.com

Echelon Neuron User Manual

Page 101

background image

Neuron Tools Errors Guide

93

NCC#

Description

393

394

395


396

Cannot add file record to dependency file (might cause build status calculation

to fail) [NCC#393]

Cannot add switch record to dependency file (might cause build status

calculation to fail) [NCC#394]

Cannot add parameter record to dependency file (might cause build failure)

[NCC#395]

Cannot write .ncdep dependency file (might cause build status calculation to fail

[NCC#396]

These problems are reported by the dependency utility. Although it will

not stop the compilation, the warning alerts the user to a potential problem

the next time a Project Make (or a build) is run, because the Project Make
utility may not be able to correctly calculate whether the project will need

to be rebuilt. To clear this condition, try a "clean" followed by an

"unconditional build".

397

Reference in NVT or CPT not found [NCC#397]

Some Network Variable Types (NVTs) or Configuration Property Types
(CPTs) can reference other NVTs. References can be nested. This message

indicates that the original type, or one of the types that it references,

references another type that does not exist in the applicable and available
resource files.
Use the NodeBuilder Resource Editor to examine the original type, and
then to observe whether all the types it references do, in fact, exist. This

problem may be caused by any of the following: one or more resource files

are missing, or the catalog does not list these resource files, some resource
files may be out of date, or possibly a resource file has been mis-edited.

398
399

Unspecified error in option processing [NCC#398]

Unspecified error in execution of compiler [NCC#399]

These messages result from an unknown program failure or anomaly that

has been caught by self-checking code in the compiler.

401

Repeated declaration of CP family does not match previous declaration

[NCC#401]

In support of code modularity, it is possible that more than one file in a

compilation may declare a CP family of the same name, and with identical
properties. Rather than force the reorganization of the code or the creation

of artificially cryptic names, the compiler supports multiple identical

declarations, and will merge these declarations into a single declaration of
the family. This feature requires the two (or more) declarations being

merged to be identical in every aspect.