Silver Dream !

I see. Thanks for trying. Do we have contact to the original contributor, maybe? In the meantime a friend of mine will try to give a stab at it too (although he also wasn't too optimistic after seeing the commit).

My question was about whether there is an easy way to check what revision the downloaded "tarball" sources were generated from. I think they're the initial 2.4, which would mean r26490 but can't be sure today. I can't compile revisions earlier than #27818. There were issues even with later ones (ffmpeg, giflib, ..) but I worked them around. With 27817 and earlier I didn't notice any fast workaround. sources are configured only with --disable-ffmpeg (starting from a revision that doesn't work anymore...

My question was about whether there is an easy way to check what revision the downloaded "tarball" sources were generated from. I think they're the initial 2.4, which would mean r26490 but can't be sure today. I can't compile revisions earlier than #27818. There were issues even with later ones (ffmpeg, giflib, ..) but I worked them around. With 27817 and earlier I didn't notice any fast workaround. sources are configured only with --disable-ffmpeg (starting from a revision that doesn't work anymore...

My question was about whether there is an easy way to check what revision the downloaded "tarball" sources were generated from. I think they're the initial 2.4, which would mean r26490 but can't be sure today. I can't compile revisions earlier than #27818. There were issues even with later ones (ffmpeg, giflib, ..) but I worked them around. With 27817 and earlier I didn't notice any fast workaround. sources are configured only with --disable-ffmpeg (starting from a revision that doesn't work anymore...

After uneven confronation with SF's SVN and its constant errors "during SSL communication" I was able to narrow it down to the following: the "original" 2.4 tarball, which I presume is revision #26490 (any easy way to check which exact revision the tarball was created from?) does not have the problem revision #27818, which seems to be the earliest I can still compile on my current machine, already exhibits the problem

Yes, moncommands is used in this case. It loads the labels.

Checked out (with many problems - sf sucks all the time) and compiled the repo version. It's still leaky: mon_lex.l:562: Warning: Memory block(s) allocated here was not free'd (Memory leak with size 0x15e at 0x7ff4a7249c00). callstack: 1 x64sc 0x00000001057612f7 lib_strdup_pinpoint + 151 2 x64sc 0x0000000105897db0 yylex + 11040 3 x64sc 0x0000000105889749 yyparse + 633 4 x64sc 0x000000010588c548 parse_and_execute_line + 136 5 x64sc 0x000000010589b9b4 playback_commands + 212 6 x64sc 0x000000010577dc9e...

You mean like revision between 2.4 and 3.0? For this I'd need more time but can possibly do.