#276 closed defect (fixed)
mbuild gives errors if .mb segment name starts with a number
| Reported by: | Eric Swenson | Owned by: | Gary Dixon |
|---|---|---|---|
| Priority: | minor | Milestone: | MR12.8 |
| Component: | Tools | Version: | MR12.7 |
| Keywords: | Cc: |
Description
If the .mb segment base name is numeric, e.g. "126.mb", it gives the following error:
mbuild
Installation_directory: >udd>sa>ejs>work>tickets>126
Scanning, with read of any build_script...
mbuild (scan): Do you want to read the 126.mb file? y
ERROR 04: Invalid build script statement on LINE 6
SOURCE: Build_script: 126.mb;
mbuild (read): Improper data in build script file. Parsing build script: >udd>sa>ejs>work>tickets>126>126.mb
mbuild:
Change History (2)
comment:1 by , 4 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 3 years ago
https://s3.amazonaws.com/eswenson-multics/public/mcrs/MCR10112.pdf
Fixed with MR12.8-1022.
Note:
See TracTickets
for help on using tickets.

This issue was repaired by a change in mbuild_script_parse_.rd described in the history comment:
6) change(2022-01-05,GDixon), approve(2022-02-01,MCR10112), audit(2022-02-01,Swenson), install(2022-02-01,MR12.8-1022): A) mbuild build script file name (and files derived from that name) need not follow rules for PL/I program names. Rename <ename> syntax function to <progName>, and create a new <ename> that makes no special requirement on 1st letter of name.