Dmitry Lyssenko

Analysis: When either of the reported failures happen (given option `-f`), they occur *after* source JSON file already open for write (and hence already truncated). One of the feasible solutions:...

Not sure if compiling was ever attempted on RPI, however, if compiler is C++14 or above, then it *should* compile - the package has no dependencies - 100% c++ code....

I kinda assumed you had a compiling issue, could you elaborate if it's something else? any logs/outputs?

Yes, your libc requires an upgrade. Most likely the solution is described [here](https://github.com/processone/ejabberd/issues/2650), namely, quoting from that page: >E.g. add deb http://ftp.de.debian.org/debian sid main to /etc/apt/sources.list and execute apt-get update...

Try googling those errors and fixing those one by one. Another solution might be finding a more modern version of RPI (with a fresher version c++) and compiling a relocatable...

Hi D4N, >tl;dr; I have noticed that jtc has a pretty impressive documentation, but no tests. - yes, `jtc` has extensive test suit using google-test framework, but I don't publish...

> all of the examples in User Guide should pass - all except this one: >

Hi, thank you for your feedback. Making `jtc` brew-able is one of the items on my to-do list. I'll try to prioritize this task among other things.

sorry, not yet. Things diverted my focus from my OSS projects, but I'm working to get that focus back. Hopefully I'll be able to get some bandwidth soon to do...

1. `lib/jtc_guide.hpp`: Hmmm, do you think debugging (`-d`) is the option regular users would ever use (and hence worth mentioning in the mini-guide)? \- If so, then why `-ddd` and...