From: mw40171@mucweb.de   
      
   On 1/14/26 15:03, Craig A. Berry wrote:   
   > I think in the days when one could not rely on a CRTL being shipped with   
   > the OS, there were mechanisms to statically link one in so you could   
   > distribute your application.  It also probably made it possible to, for   
   > example, build on v5.x and deploy to a mix of v4.x and v5.x systems, or   
   > mix VAX C and DEC C modules.  This is a vague memory of a mechanism I   
   > never used myself, so this may not be quite right, but something like   
   > that is the origin of the RTLs Gerard is talking about.   
      
   Obviously there is not enough information about how and for what these   
   translated images are used. They are shareable images, not object   
   libraries. So it's not about statically linking.   
      
   On the other hand, if they are needed in a link operation on Alpha or   
   IA64, then you have a native object module. From that I conclude, that   
   some source code was compiled on Alpha/IA64.  But then it should be   
   possible to avoid referencing the translated shareable images at all. At   
   least I think, it should be possible. But without more information ...   
      
   If you link on Alpha or IA64, you can create a map file, which tells you   
   what is referenced from these shareable images. There are also some   
   tools that show you what a shareable "Image Exports" and show you the   
   "eXternal Procedure and Data list" of an image. But. analyze/image is   
   your friend and can help even if you do not have these tools.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)