Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 15100  |
|  Bj”rn Wiberg to Alisha Stutz  |
|  Re: ruling out  |
|  01 Jan 23 15:50:56  |
 TID: Mystic BBS 1.12 A48 MSGID: 2:201/137 a8e7d3f0 REPLY: 2:301/113 11955c33 TZUTC: 0100 Hello Alisha! Happy New Year! On 01 Jan 2023, Alisha Stutz said the following... AS> As i write months ago, this is the only way for modern Debian/Ubuntu to AS> work with Cryptolib and Mystic BBS. Following my Steps and it works. When I compiled/installed cryptlib 3.4.5 with gcc 10 on Debian 11, I used this (sorry for any unintended linebreaks): wget https://cryptlib-release.s3-ap-southeast-1.amazonaws.com/cryptlib345.zip unzip -a cryptlib345.zip # for gcc version 10 (existing logic incorrectly detect/interprets # this as gcc 1.0) sed -i 's/if \[ "$GCC_VER" -ge 45 \]/if [ "$GCC_VER" -eq 10 ] || [ "$GCC_VER" -ge 45 ]/g' tools/ccopts.sh make shared ln -s libcl.so.* libcl.so mkdir -p ~/cryptlib /bin/cp -df libcl.so* ~/cryptlib/ ...and then set LD_LIBRARY_PATH for Mystic (MIS) to ~/cryptlib, e.g. /home/bbs/cryptlib. Maybe the version detection ought to be removed altogether. I wonder how many that are using gcc < 4.5 nowadays when compiling cryptlib... Best regards Bj”rn --- Mystic BBS v1.12 A48 (Linux/64) * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137) SEEN-BY: 1/123 15/0 90/1 105/81 106/201 120/340 123/131 129/305 153/7715 SEEN-BY: 201/0 137 203/0 124 221/1 226/30 229/110 111 112 113 114 SEEN-BY: 229/206 275 307 317 400 424 426 428 452 470 550 664 700 230/0 SEEN-BY: 261/38 266/512 280/464 282/1038 292/854 8125 317/3 320/219 SEEN-BY: 322/757 335/364 342/200 396/45 460/58 633/280 712/848 3634/24 SEEN-BY: 5020/1042 PATH: 201/137 0 203/0 292/854 229/426 |
[ << oldest | < older | list | newer > | newest >> ]