TZUTC: -0700   
   MSGID: 52525.syncprog@1:103/705 2cff102e   
   PID: Synchronet 3.21a-Linux master/d7c78e2c2 Aug 09 2025 GCC 12.2.0   
   TID: SBBSecho 3.29-Linux master/5e4076dbf Aug 09 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: UTF-8 4   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/commit/c643f673c3efd05c2898945b   
   Added Files:   
   	3rdp/build/cl-no-stdc-flexarray.patch   
   Modified Files:   
   	3rdp/build/GNUmakefile   
   Log Message:   
   Fix SF ticket 205   
      
   When using GCC >= 15, Cryptlib attempts to use flex arrays.   
   However, the implementation seen in CachyOS at least, sizeof()   
   a struct ending with a flex array doesn't include padding before   
   the first element of the array.   
      
   Because of this, Cryptlib will write to memory after the allocation.   
   This gets caught by the -fhardened fortify source memcpy()   
   implementation, so the process crashes during the cryptlib self-test.   
      
   To "fix" this, I'm just disabling the use of flex arrays, and falling   
   back to inserting an extra byte at the end, which uses the "classic"   
   method to do this, but make unaligned access much more likely on   
   LLP64/LP64 systems (ie: most current systems as of 2025).   
      
   Luckily, it's also pretty normal to natively support unaligned access   
   these days, so this is better than the alternative and easier than   
   fixing it right.   
   --- SBBSecho 3.29-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 700 705 240/1120 5832 263/1 266/512   
   SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 467/888 633/267   
   SEEN-BY: 633/280 384 418 420 2744 712/848 770/1 902/26 5020/400 5075/35   
   PATH: 103/705 280/464 633/280 229/426