Leandro provided the final clue. :) I suspect avahi-tqt should build against either Qt3 or TQt3. I don't know whether we need to modify the patch. I won't push to GIT unless a global solution exists that works for all distros. There are so many of these little paper cut build issues that sit idle in the bug tracker. These issues need to be resolved so everybody can build these packages on any distro without special patching. According to Tim's previous post these kinds of things should not happen, but they are. Would be nice if one day (soon) we quashed these many bugs. :) The solution used for avahi-tqt works with kstreamripper too, but I still can't build kstreamripper. The errors now have something to do with undefined reference to vtable. I tried adding kdemacros.h to the preprocessor includes of the affected files, but that did not help. I hate being a C++ noob-boob. Darrell

In this case, I was instructed to change A to B. Made sense to me and the problem was solved. Yet I can't yet hack C++ code from scratch. I perform an occasional copy and paste, add a snippet here and there, but overall, C++ still baffles me with classes and funky syntax. Something complains about an undefined reference. I know what the message means, but I don't know how to solve the problem inside this project because the code base is so huge. With this project I have little idea where most of the classes and functions are written throughout the entire code complex. Adding a simple check box is complicated. There are read functions, write functions, user interface specs, connection signals, etc. I'm sure there is a pattern to all of this. I just haven't figured out where to start. I can get fairly riled over some of this stuff too. Then, after I expel much gas and calm, I remember one of the great lessons I have to relearn every day: humans are creatures of limited knowledge. That is, the universe is not bigger than we know, but bigger than we can know. There are too many variables in every equation of life. Somewhere, one day, somebody noticed in the g++ compiler that certain rules of compilation were not being adhered to as intended or expected. Or the standard changes and the rules change. So the compiler is updated with stricter rules. Shit breaks. We get mad. If I had the experience necessary, I merely adjust the problematic code to the more anal standard and recompile. I don't have those skills. Nor you. Yet. So we get frustrated because some twit in compiler land got anal. You and I get frustrated because we have to wait for somebody else to solve the compilation problem. Or spends hours and hours searching the web in the slim hope we find our solution. With our lack of skills more often than not we don't recognize the solution anyway, but we search because that is our nature. We get further frustrated because of late, this list is dead. Days pass before somebody responds. Maybe. I lost count how many unanswered questions I have posted. So we head back to the web further banging our heads hoping we might recognize something --- anything --- that might succeed. And we seldom do. Then two weeks later a guru shows up with a one-liner solution. How does that old adage go? Seek peace to accept what we cannot change, courage to change what we can, and wisdom to know the difference. A 2x4 upside the mule's head rarely ever worked. I should post questions, go do yard work and read books for two weeks and then return. Probably far less frustration. Darrell