REPLY: 1:153/757.0 5dd56139
MSGID: 2:280/464.47@fidonet 5dd6d92d
CHRS: UTF-8 4
TZUTC: 0100
TID: CrashMail II/Linux 1.7
 OT>> Is anyone using Squish on Linux? The sources from github [1]
 OT>> don't build with any recent gcc (I even trid gcc4.9). Compile
 OT>> errors an a ton of warnings.

 AI> Not since around 2004, maybe.

 OT>> [1] https://github.com/sdudley/maximus

 AI> I never knew it was on github but that's where everything seems to be
 AI> today.

I don't like the Github monoculture, but everything is better than
Sourceforge. I'm using Gitlab for my own projects.

 AI>  I used the 3.03 sources from sourceforge.net and the sources at
 AI> github look much the same.

I think they are the same.

 AI> Back then I think gcc was at version 2.95 or somewhere there abouts.

IIRC there were some commits for compatibility with gcc 3 (dot something).
Unfortunetely I don't know enough of C / C++ to fix the errors and warnings
properly. I don't think it would be hard for a C coder, but it seems nobody is
interested in Squish and Maximus on Linux anymore. Or should I ask in the TUB
echo?

 AI> I didn't use squish a lot but it seemed to work the way it always did
 AI> in DOS and OS/2. I vaguely recall some visual glitches but
 AI> functionality seemed to be good, at that time.

I used Squish and Maximus in the 90s and it still can compete with recent Fido
software. I managed to compile parts of it on the Raspberry a while ago, but
was not sure if my changes were correct or would cause other problems at
runtime.

There was problem with rescanned echoareas I received from my uplink. Because
todays computers and drives are so much faster, all .pkt files had the same
timestamp. Squish tries to toss .pkt files chronologically, but fails
misserably in that case and tosses the .pkt files in random order.

Do I have to learn C or write my own tosser in REXX? ;)


--- GoldED+/LNX 1.1.5-b20180707
 * Origin: * nigirO (2:280/464.47)
SEEN-BY: 1/123 15/2 18/200 90/1 103/705 203/0 221/0 227/114 229/354
SEEN-BY: 229/426 452 1014 240/5832 249/206 317 400 280/464 5003 292/854
SEEN-BY: 317/3 322/757 342/200 396/45 423/120 633/280 712/848 770/1
SEEN-BY: 2452/250
PATH: 280/464 229/426