Hi mark,

On 2022-01-20 16:28:16, you wrote to me:

 ml>>> my configure and compiling output appear to be ok for the most
 ml>>> part... configure doesn't complain loudly about anything and
 ml>>> compiling shows a few warnings about format-overflow where some
 ml>>> things may possibly write more than 12 bytes to a region or
 ml>>> destination of only 12 bytes in readcfg.c... the only other warning
 ml>>> is a misleading indention in https.c where an if statement is
 ml>>> apparently missing the "{}" around the two Log() lines it appears to
 ml>>> be protecting... lines 372-374...

 WV>> That was a long time ago in my case, and I didn't save the output. ;)

 ml> my build script logs all output via tee... makes it easy for me see things
 ml> as they happen and enables me to look back at previous builds output :)

On the compile I just did (it wasn't a full build), just a make on the new files from 111 to 113. I only got a couple of warnings:

Compiling md5b.c...
md5b.c: In function ?MD5Update?:
md5b.c:134:4: warning: call to function ?MD5_memcpy? without a real prototype [-Wunprototyped-calls]

And then a couple of dozen more on other functions in the md5b.c file. So nothing related to the reloading-config-crash problem...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815