Message: previous - next
Month: September 2010

Re: [trinity-devel] Building kdebase with svn 1173506

From: Darrell Anderson <humanreadable@...>
Date: Thu, 9 Sep 2010 13:14:22 -0700 (PDT)
> Looks like you are getting much closer!  Try it again
> with revision
> 1173590 or above.

Okay. Updating svn now as I write and will try again.

> For some reason when I do a build test here these issues
> don't show up, so
> something is different (stricter?) under Slackware.

I would not know. :( I wish I could help. There are many Slackers who could answer your question. Getting them involved is something else.

Some people might argue Slackware is "more pure" than Debian with respect to patching upstream code. Generally, that probably is correct. Patrick Volkerding tends to resist patching upstream sources. He patches as often as necessary to get things to function in Slackware, but prefers to provide upstream tools as intended by the upstream developers. Possibly then a missing include file works on your setup because you have and expect Debianized sources where that won't be true with Slackware.

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?

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.

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.