This is getting to be a bit off course for this forum, but just a quick note to say that I checked the boost installation files in YaST and there is a package installed that is C++ *.so (shared object) libraries. Then I told YaST to delete the libraries (which I wouldn’t have actually completed), and it did indeed show a number of dependencies for YaST. I’m kind of surprised that YaST would use something that obscure, but there you have it.

Jim

Further above you wrote: “I also tried to update boost, but that killed yast dead…”.
Boost is headers only. I think some special parts of boost can actually be compiled as shared libs but even if, yast is most certainly not linked against such a freak. In fact, I even believe yast is statically linked but I am not on SuSE to confirm that
But I can confirm that tint compiles on recent systems. On my system, I have compiled all relevant libraries (atk, pango, glib, GTK, wx…) myself and that worked. I only had trouble with scons but since I would not use it for anything else, I compiled and linked tint manually without any trouble.

F.

+1 to Jimmy’s feature request. It might also be helpful to let the user choose which color groups are needed. For example, in some cases I am looking for a detailed separation of the different shades of green in a picture, while in other cases I’d like green to be abolished altogether, regardless of the shade. Maybe a nice color selector component in which the user can place markers where clusters should be located?

Thomas

Did you update wxWidgets and wxGTK through pre-made RPMs from the various SuSE sites, or did you compile them yourself?

I also tried to update boost, but that killed yast dead and I had a heck of a time getting that back.

Could you list the ‘exact’ versions of lib’s you are using if the minor numbers aren’t included in the README.txt file?

TIA,

Jim

I compiled in debug mode yesterday and got some consistent errors regarding:

“wxAssertFailure” failed in Insert()”

also problems with:

“wxGridBagSizer”

I tried updating ‘boost’ and that was a BIG mistake as yast depends on the specific version included with SuSE 10.2; so I spent a few hours finding and getting the proper libs back (I hope … at least yast is working again).

My next step is to remove scons from the picture, but I’m not convinced that using the same compile args will do anything different.

Have you considered releasing a Linux binary? Could I get a copy of your SuSE 10.2 binary to see if it works on my box?

TIA

Jim

Jim — I’m at a bit of a loss on this one, so apologies that I haven’t been able to help more. I did get some reports from the alt linux crew about some issues with scons that were causing build problems for them. They have a patch together for scons that they’re sorting out. The particular problem was unrelated to your’s (–as-needed compiler flag), but this does suggest that scons may be the issue in your case too. You could try compiling everything without scons — there are no tricks to it, just compile each file in the src directory and link them all up. The compiler flags that scons is using are in the config.py file.

Debug] 03:57:58 AM: ./src/common/gbsizer.cpp(687): assert “wxAssertFailure” failed in Insert(): Insert should not be used with wxGridBagSizer.
Trace/breakpoint trap
jim@mugsy:~/programs/tint/tint-1.0.1> ./tint
[Debug] 04:02:53 AM: ./src/common/gbsizer.cpp(687): assert “wxAssertFailure” failed in Insert(): Insert should not be used with wxGridBagSizer.
Trace/breakpoint trap
jim@mugsy:~/programs/tint/tint-1.0.1>

I’ve scoured the web and don’t find much relating to this. Any help out there?

TIA

Jim

I probably will have to recompile the world with the debug option, but I’m not looking forward to that as it ends up to be a twisty mess getting everything compiled so the binary will run without a mismatch error.

My other option is to reload SuSE 10.2 and see if a clean install fixes the problem. I’m somewhat leery of that as I don’t have many changes in place right now.

Thanks for your advice.

Jim

Frank