Error by compiling MKK utility


Topic author
spoofy
Contributor
Posts: 21
Joined: Fri Mar 31, 2023 6:02 pm
Reputation: 0
Location: Erlangen/Germany
Status: Offline

Error by compiling MKK utility

Post by spoofy » Thu Apr 20, 2023 7:20 am

I tryed to compile MKK utility: https://github.com/endlesssoftware/mmk
and CC Crashed.

Code: Select all

$ @compile

   MMK Bootstrap Procedure

$! If you have the SDL compiler installed, then feel free to uncomment the
$! lines below.  However, it is not absolutely necessary as the resulting
$! header files are distributed with the source kit.
$!
$!$ MESSAGE/NOOBJECT/SDL=MMK_MSG.SDL MMK_MSG.MSG
$!$ SDL/VAX/LANGUAGE=CC=ETC_DIR:MMK_MSG.H MMK_MSG.SDL
$ LIBRARY/CREATE BIN_DIR:MMK.OLB
$ CC/NOLIST/OBJECT=BIN_DIR:MMK.OBJ MMK.C
$ LIBRARY/REPLACE BIN_DIR:MMK.OLB BIN_DIR:MMK.OBJ
$ CC/NOLIST/OBJECT=BIN_DIR:FILEIO.OBJ FILEIO.C
$ LIBRARY/REPLACE BIN_DIR:MMK.OLB BIN_DIR:FILEIO.OBJ
$ CC/NOLIST/OBJECT=BIN_DIR:MEM.OBJ MEM.C
$ LIBRARY/REPLACE BIN_DIR:MMK.OLB BIN_DIR:MEM.OBJ
$ CC/NOLIST/OBJECT=BIN_DIR:GET_RDT.OBJ GET_RDT.C
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=000000000343
0000, PC=00000000006C9993, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image     module    routine               line      rel PC           abs PC     
DECC$COMPILER  GEM_VER_AREA:<SRC>GEM_IC.BLI;1  CHECK_ATTRIBUTES
                                          #816 00000000006C9993 00000000006C9993
DECC$COMPILER  GEM_VER_AREA:<SRC>GEM_IC.BLI;1  CHECK_TUPLE
                                         #1564 00000000006CD141 00000000006CD141
DECC$COMPILER  GEM_VER_AREA:<SRC>GEM_IC.BLI;1  CHECK_TUPLE_IN_LIST
                                         #2145 00000000006D0461 00000000006D0461
DECC$COMPILER  GEM_VER_AREA:<SRC>GEM_IC.BLI;1  GEM_IC_CHECK_NODE
                                         #2635 00000000006C80BA 00000000006C80BA
DECC$COMPILER  GEM_VER_AREA:<SRC>GEM_IC.BLI;1  GEM_IC_CHECK_NODE
                                         #2671 00000000006C83EE 00000000006C83EE
DECC$COMPILER  GEM_VER_AREA:<SRC>GEM_IC.BLI;1  GEM_IC_CHECK
                                         #2276 00000000006C69BE 00000000006C69BE
DECC$COMPILER  [.src]g2l_module.cxx  G2L_COMPILE_MODULE
                                          #571 0000000000A490D3 0000000000A490D3
DECC$COMPILER  GEM_VER_AREA:<SRC>GEM_CO.BLI;1  GEM_CO_COMPILE_MODULE
                                         #3413 00000000006E2627 00000000006E2627
DECC$COMPILER  COMPILE.C;1  gemc_be_master
                                       #103705 00000000004236FE 00000000004236FE
DECC$COMPILER  COMPILE.C;1  gem_xx_compile
                                       #102916 00000000004223D7 00000000004223D7
DECC$COMPILER  GEM_VER_AREA:<SRC>GEM_CP_VMS.BLI;1  GEM_CP_MAIN
                                         #2643 00000000006D4C1E 00000000006D4C1E
DECC$COMPILER                                0 0000000000AD76D4 0000000000AD76D4
DECC$COMPILER                                0 00000000020F6D6D 00000000020F6D6D
PTHREAD$RTL                                  0 000000008004122C FFFF830008D0322C
PTHREAD$RTL                                  0 0000000080002316 FFFF830008CC4316
                                             0 FFFF8300071FBDC6 FFFF8300071FBDC6
DCL                                          0 000000008006741B 000000007ADFF41B
%TRACE-I-LINENUMBER, Leading '#' specifies a source file record number.
%TRACE-I-END, end of TRACE stack dump
$BAIL_OUT:
$ EXIT 1.or.(0*F$VERIFY(0))
$ cc/version
VSI C X7.4-726 (GEM 50X23) on OpenVMS x86_64 E9.2-1  
$ 


Last edited by mister.moderator on Thu May 25, 2023 3:04 am, edited 1 time in total.

Tags:


sms
Master
Posts: 317
Joined: Fri Aug 21, 2020 5:18 pm
Reputation: 0
Status: Offline

Re: Error by compiling MKK utility

Post by sms » Thu Jun 08, 2023 7:47 pm

Code: Select all

> Could you put it up for general download via link?

   Loose use-at-own-risk source files with (and without) my changes:

      http://antinode.info/ftp/mmk/mmk-master_2023-04-20/

   descrip.mms          Added COM1 macro for use with the cross-tools.
                        ("COM1=SYS$MANAGER:X86_XTOOLS$SYLOGIN.COM")

   get_rdt.c            Changed to use <lbr$routines.h> instead of
                        (lame) private declarations.

   mmk.c                Changed to test __VAX instead of multiple modern
                        architecture macros.
                        Added built-in macro "MMSX86_64" on x86_64.

   mmk_compile_rules.c  Changed to test __VAX instead of multiple modern
                        architecture macros.

   parse_descrip.c      Changed to test __VAX instead of multiple modern
                        architecture macros.
                        
   parse_objects.c      Changed to test __VAX instead of multiple modern
                        architecture macros.
Added in 2 hours 47 minutes 3 seconds:

Code: Select all

   On a (slightly) related topic, the HELP for the following product
could use an update:

V87 $ mms /id
%MMS-I-IDENT, MMS V4.0-4 © Copyright 2022 VMS Software, Inc and Hewlett-Packard 
Development Company, L.P.


   Who can spot what's missing?

V87 $ help mms descrip reserve

MMS

  Description_File

    Reserved-Macros


         MMS                  Used to invoke MMS from a description file.
         MMSALPHA             Defined as 'Alpha' if MMS is running on Alpha.
         MMSARCH_NAME         The architecture name on which MMS is running
                                  (i.e. 'IA64', 'Alpha' or 'VAX').
         MMSDESCRIPTION_FILE  The full file specification of the description
                              file specified (or implied) by the command line.
         MMSIA64              Defined as 'IA64' if MMS is running on IA64.
         MMSQUALIFIERS        The command line qualifiers used to invoke MMS.
         MMSTARGETS           The target list specified on the command line.
         MMSVAX               Defined as 'VAX' if MMS is running on VAX.

         Note: the MMSIA64, MMSVAX and MMSALPHA macros can be used with the
               .IF directive to include description file lines that should
               only be processed for the appropriate architecture.

Post Reply