From: arne@vajhoej.dk   
      
   On 1/14/2026 7:25 AM, gcalliet wrote:   
   > Le 13/01/2026 à 20:40, Simon Clubley a écrit :   
   >> On 2026-01-13, Arne Vajhøj  wrote:   
   >>> On 1/13/2026 10:35 AM, gcalliet wrote:   
   >>>> I begin the year - I hope successfull, happy, and with a good health   
   >>>> for   
   >>>> everyone with a somehow prehistoric question.   
   >>>>   
   >>>> Some applications, in general using x11, where linked with this sort of   
   >>>> library:   
   >>>> VAXCRTLG_D56_TV_AV.EXE;1   
   >>>> VAXCRTLG_D56_V73_TV_AV.EXE;1   
   >>>> VAXCRTL_D56_TV_AV.EXE;1   
   >>>> VAXCRTL_D56_V73_TV_AV.EXE;1   
   >>>>   
   >>>> There are been vesting from VAX to alpha, and doing the same sort of   
   >>>> operation to itanium.   
   >>>>   
   >>>> What has been done for x86? I know some applications using this sort of   
   >>>> libraries, and without them it's impossible to go ahead.   
   >>>>   
   >>>> What has been done? What can be done?   
      
   >>> There were VEST (VAX->Alpha) and AEST (Alpha->Itanium),   
   >>> but no IEST (Itanium->x86-64).   
   >>>   
   >>> Explicit VSI decision I believe.   
   >>>   
   >>> But it is not clear to me what you need.   
   >>>   
   >>> Many years ago, but as I remember it then if you VEST'ed   
   >>> FOOBAR.EXE then you needed a VEST'ed RTL's, but if you   
   >>> compiled and linked FOOBAR then you used the normal RTL's.   
   >>   
   >> Indeed. I wonder why Gerard cannot just recompile the application   
   >> as normal.   
   >>   
   >> Missing source code ?   
   >>   
   >> Missing Compiler/tools ?   
   >>   
   >> Is this some Ada code he's trying to get working on x86-84 ?   
   >>   
   >> Unless I am mistaken, Arne is correct and this approach stops at Itanium   
   >> and cannot be carried forward to x86-64.   
      
   > Thanks for the answers. I knew there are been Vest and Aest, and that   
   > VSI said there will not be any "Iest".   
   >   
   > These specific RTL were used in the context of rendering picture by   
   > Motif+x11. You needed them in the link phase.   
   >   
   > I don't remember why Digital/Compaq/HP created these Vested and Aested   
   > RTL. However the source code of them has never been accessible for   
   > users. I hope Digital/Compaq/HP had the sources but/and I don't know the   
   > specific issues which involved their choice of Vesting and Aesting them.   
   >   
   > As a technical point, it is a very interesting subject.   
   >   
   > But in the term of a port to x86, it could be a blocking point. I'm just   
   > in the beginning of investigation on that. I'm not sure the applications   
   > I have to analyze really use these libraries. I only remember that I   
   > made a port to Itanium of similar applications ten or twenty years ago,   
   > and it has been helpfull getting Aested libraries.   
      
   Still puzzled.   
      
   You have a VAX with foobar.c that you compile   
   and link with vaxcrtl on VAX to produce   
   foobar.exe.   
      
   You copy foobar.exe to Alpha and VEST it. Due to some   
   incompatibility the new Alpha image is not satisfied   
   with decc$shr but require a vaxcrtl*tv*.exe.   
      
   If you had compiled foobar.c and linked it normally   
   on Alpha then decc$shr would have been enough.   
      
   If you move an Itanium foobar.exe to x86-64 then you   
   can't IEST it and you therefore do not have a need for   
   any *tv*.exe.   
      
   You have to compile and link normal.   
      
   Your Motif application should be able to link on   
   VMS x86-64 with what is there I think.   
      
   $ dir sys$share:decw$*.exe   
      
   Directory SYS$COMMON:[SYSLIB]   
      
   DECW$AILSHR.EXE;1   DECW$AILSHRR5.EXE;1 DECW$BKRSHR.EXE;1   
   DECW$BKRSHR12.EXE;1   
   DECW$D2DXLIBSHR.EXE;1                   DECW$DWTLIBSHR.EXE;1   
   DECW$DXMLIBSHR.EXE;1                    DECW$DXMLIBSHR12.EXE;1   
   DECW$ICELIB.EXE;1   DECW$ICELIB_PTHREAD.EXE;1   
   DECW$LBXUTIL.EXE;1   
   DECW$LCNLIBSHR.EXE;1                    DECW$LOGINOUT.EXE;1   
   DECW$MAILSHR.EXE;1   
   DECW$MAILSHR12.EXE;1                    DECW$MRMLIBSHR12.EXE;1   
   DECW$PRINTWGTSHR.EXE;1                  DECW$SECURITY.EXE;1   
   DECW$SECURITY_VMS.EXE;1   
   DECW$SESSIONSHRP.EXE;1                  DECW$SETSHODISSHR.EXE;1   
   DECW$SMSHR.EXE;1    DECW$TERMINALSHR.EXE;1   
   DECW$TERMINALSHR12.EXE;1   
   DECW$TRANSPORT_COMMON.EXE;1             DECW$TRANSPORT_DECNET.EXE;1   
   DECW$TRANSPORT_LAT.EXE;1                DECW$TRANSPORT_LOCAL.EXE;1   
   DECW$TRANSPORT_TCPIP.EXE;1              DECW$UILSHR.EXE;1   
   DECW$XAUSHR.EXE;1   
   DECW$XEXTLIBSHR.EXE;1                   DECW$XLIBSHR.EXE;1   
   DECW$XMLIBSHR.EXE;1   
   DECW$XMLIBSHR12.EXE;1                   DECW$XMULIBSHR.EXE;1   
   DECW$XMULIBSHRR5.EXE;1                  DECW$XPORT_PTHREAD.EXE;1   
   DECW$XPORT_SERVICES.EXE;1               DECW$XTLIBSHRR5.EXE;1   
   DECW$XTRAPLIBSHR.EXE;1                  DECW$XTRAPLIBSHRR5.EXE;1   
   DECW$XTSHR.EXE;1   
      
   What is missing?   
      
   Or to recap for x86-64:   
   * if you do not have the source or the compiler then you   
      are out of luck   
   * if you have source and compiler then just compile and   
      link - dropping anything *tv* from the link   
   * if you get link errors about missing stuff then start hunting   
      for those   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)