From: craigberry@nospam.mac.com   
      
   On 9/5/25 6:55 AM, Waldek Hebisch wrote:   
      
   > I now got to C++ problem.  In fact, this may be binutils problem:   
   > gcc generates an assember file and as from binutils-2.21 aborts on   
   > this file.  as from current binutils developement tree produces   
   > error message instead:   
   >   
   > pom/kompi/gcc/binu-build3/gas/as-new -o array_type_info.obj array_type_info.s   
   > array_type_info.s: Assembler messages:   
   > array_type_info.s: Error: no entry symbol for global function    
   _ZN10__cxxabiv117__array_type_infoD1Ev'   
   >   
   > The offending function is defined in the following way:   
   >   
   >          .globl _ZN10__cxxabiv117__array_type_infoD1Ev   
   >          _ZN10__cxxabiv117__array_type_infoD1Ev = _ZN10__cxxab   
   v117__array_type_infoD2Ev   
   >   
   > If I delete this definition and the ony use of it the file assembles OK.   
   > AFAICS this means that _ZN10__cxxabiv117__array_type_infoD2Ev is correctly   
   > defined.   
      
   Note that this symbol is 38 characters long.  The native VMS toolchain   
   traditionally limits itself to 31-character symbols and uses a checksum   
   to shorten symbols that are longer.  The linker, the librarian, and the   
   inertia of existing code are all things I've heard blamed for this state   
   of affairs.   
      
   I have no idea whether the tools you are using require or are capable of   
   observing the 31-character limit.  If some parts do and other parts   
   don't, that could obviously cause trouble, and of course you've got the   
   C++ name mangler in the mix as well.   
      
   If you need an open source name shortener that mimics what the DEC   
   compilers do, I've got one here:   
      
      
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)