mbuild unclear/bogus warnings when ADDing new Components & other mbuild bugs

[Gary Dixon]

Four improvements are needed in the mbuild subsystem to repair installation issues.

1. DELETE of an existing bound segment coupled with ADDing one or more of its component sources to another existing bound segment can lead to the following issues:

• Bogus warning message that the source component is not mentioned in the build script.

• Warning message contains insufficient information about the unhandled source component to identify the underlying problem.

2. ADDing a new source component to an existing bound segment encounters an issue:

• mbuild treats the existing bound segment as if it were being ADDed, causing bogus errors during archive_prep and install_ec operations.

3. REPLACE of >sss>pl1.dcl data file generate bogus messages about source file not appearing in build script, because mbuild_info_ data base entry for .dcl suffix references an invalid default_library = “standard.execution”. It should be: sss.execution

4. ADDing a new source component causes any derived object compiled from that source to be cleaned up twice during an mbuild clean request.

[Gary Dixon]

MCR10117 Issue Details

[Eric Swenson]

Fixed with MR12.8-1029