<snip>
I notice from some of the patches you make that the tqtinterface layer contributes to some of the differences. In several of the patches all you did was add a single tqtinterface include file. Possibly your system finds those files but can't on Slackware without explicit declaration. Is there a way you can configure or test your system for strict explicit declarations?
Not easily it would seem. If this keeps up I will need to install Slackware on a VM here, but that will take a few days when downloads are included and also would require me to have a current copy of your build script(s).
You never have shared that adding all of these specific include file patches cause failures on your build system for Debian and Kubuntu. Thus I'm guessing these patches probably make the system more robust and less prone to other errors. I suspect that is a good thing despite being an awkwardly slow process to get this to work on Slackware.
You are correct; each change does not break Debian, but instead seems to make the build process more robust.
I realize there is MUCH to know with what needs to be repaired with these errors. Yet is there some guidelines I can follow to try to patch things here? Yes I have other things to do and a little patience doesn't hurt, but sure would be nice if I could try to find a simple patch here and test rather than wait for you to patch. A little frustrating for me and I know you're swamped. If I could learn to understand some of the error messages I could expedite this process a tad.
Generally what I do is look for a class name at the failing line number, then search the entire Trinity source directory for <classname>::<classname>, where <classname> is the class name you found referenced in the failing file. When I find it, I look for a .h header file with the same name, then include that in the failing file.
Hope this helps!
Tim