From: craigberry@nospam.mac.com   
      
   On 9/29/25 3:01 PM, hb0815 wrote:   
   > On 9/29/25 18:17, Waldek Hebisch wrote:   
   >   
   >> Now about troubles.  VMS C functions use different name at C level   
   >> and different in libraries.  Moreover, while offically function is   
   >> available in "imagelib.olb", actual function is in a different library   
   >> and this library is needed for succesful linking.  So, one needs   
   >> to know real name of a given function and teach gcc to use it.   
   >   
   > Yes, for example, printf in the source code is changed  to DECC$GXPRINTF   
   > in the object module. DECC$GXPRINTF is a symbol in the shareable image   
   > library IMAGELIB.OLB. Symbols in a library must be unique. That explains   
   > the DECC$ prefix. I don't know what the GX means or where it comes from.   
   > I also don't know where the mapping/replacement table is.   
   >   
   > IMAGELIB.OLB contains only the symbol and a link to the shareable image.   
   > The actual code (and data) is in the shareable image, not in a library.   
   > So if you link using IMAGELIB.OLB you link with DECC$SHR. At least on   
   > Alpha, the symbol DECC$GXPRINTF is also in STARLET.OLB. By default this   
   > OLB is not used, by default you dynamically link and not statically. Do   
   > a link on VMS/Alpha with a map file. In the map you will only see   
   > DECC$SHR, no STARLET.OLB and no IMAGELIB.OLB.   
   >   
   Surely GXPRINTF knows how to format G_FLOAT numbers and there would be   
   other versions for X_FLOAT, D_FLOAT, etc.?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)