From: mw40171@mucweb.de   
      
   On 9/16/25 21:24, Waldek Hebisch wrote:   
      
   > I have made a simple-minded generator of fake shared libraries.   
   > Using fake 'DECC$SHR.exe' containing just 5 real symbols (and   
   > hundreds of dummies to fill unused positions in symbol vector)   
   > I managed to link on Linux a simple "Hello from VMS" program   
   > and the program run correctly on VMS.   
   >   
   > I still have a problem: ATM I do not know how access to variables in   
   > shared images works.  So I have bogus reference to 'C$_EXIT1'.   
      
   I don't see C$_EXIT1 in DECC$SHR on Alpha (Eisner, V8.4-2L2).   
      
   C$_ are message codes, for example C$_ENOENT (%C-F-ENOENT, no such file   
   or directory). That is integer literals.   
      
   Read/write data symbols are as procedure symbols with EGSY$V_NORM clear.   
   Literals symbols are as data with EGSY$V_REL clear.   
      
   Create a small shareable image on VMS/Alpha with a procedure, data and   
   an integer literal and you will see the flags and the differences in the   
   values. With analyze/image or a full map you should be able to find the   
   symbol vector in dump's output.   
      
   > I have noticed that VMS linker inserts reference to 'LIB$INITIALIZE',   
   > while with my fake libraries GNU linker does not reference this   
   > function.   
      
   The linker does not insert such a reference. If the LIB$INITIALIZE   
   module is included in the image, then it was explicitly included or   
   there was a reference to a symbol defined in this module from one of the   
   to be linked object modules.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)