On 2022 Jan 20 16:49:30, you wrote to me:

 WV>>> I start it with '-Cq' options,

 ml>> 'q'?? hummm... ahhh... quiet mode... ok... i run in a console terminal
 ml>> so i want to see all of that :)

 WV> Mine is run on system startup as a systemd.service. So there is no console
 WV> to look at. If I want to see what's going on I have a look at the log...

i can understand that... i have both going on... when i'm really digging into something, i set the conlog level higher and make liberal use of my scrollback buffer ;)

 ml>> that's interesting... what is your linux and compiler, please?
[...]
 ml>> gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0

 WV> gcc (SUSE Linux) 4.8.5

ahh... i know there are a lot of changes between gcc4 and gcc7...

 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. ;)

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

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
...     Oh! Ms. Co-Moderator!
---