Opened 3 years ago

Closed 12 months ago

#319 closed defect (fixed)

mbuild analyze request prints spurious warning when examining Unbound_obj requests.

Reported by: Gary Dixon Owned by: Gary Dixon
Priority: major Milestone: MR12.9
Component: Tools Version: MR12.8
Keywords: Cc:

Description

When installing an Unbound_obj which is not part of larger bound_XXX_ object segment, mbuild analyze request often displays a spurious warning message indicating it does not know which existing library segment is being replaced.

mbuild:  az
mbuild (analyze): Non-unique library paths. Seg(Unbound_obj): release_tools_libraries_  matches several library paths:
  >lib>release_tools>object>release_tools_libraries_
  >lib>release_tools>execution>release_tools_libraries_

By the time it completes its analysis, the analyze request has decided how/where to install the changed file. Its earlier indecision was finally resolved.

But there should be some way for the analyze request to provide clues to mbuild primitives that would avoid display of the spurious warning. That is the defect being reported.

Change History (2)

comment:1 by Gary Dixon, 3 years ago

Owner: changed from Eric Swenson to Gary Dixon
Status: new → accepted

I’ve figured out how to make mbuild analyze request give a clue about which of the two paths

should be chosen when it is creating the UNBOUNDOBJ structure describing the object compiled
from release_tools_libraries_.ld. With this clue, no warning gets issued.

Version 0, edited 3 years ago by Gary Dixon (next)

comment:2 by Eric Swenson, 12 months ago

Resolution: → fixed
Status: accepted → closed
Version: → MR12.8

​https://s3.amazonaws.com/eswenson-multics/public/mcrs/MCR10140_mbuild_v1.2.pdf

Fixed in MR12.9-1002.

Note: See TracTickets for help on using tickets.