I thought it was Qt you were having problems with, and it was a problem with a macro that conflicted with a variable name used in one of the Qt functions, causing a really weird error.

I’ve tracked that one down, and all you need to do is hack the Qt source file in question and #undef the macro. Works fine here - see <1110302571.534.11.camel@bucket.localnet> .

A similar fix was needed in the Scribus sources, in sciten.h, but otherwise things worked ok.

I should note that Qt built without RENDER support. I’d like to look at that some time, since without RENDER it’s pretty ugly, but ... time, time, time.—Craig

Qt caused all sorts of grief, but once they posted the mkheaders note, it seemed to compile fine. (It would compile, but without the thread support Scribus needed, no matter what I did.) Since then, Qt has compiled fine the two other times I built it from scratch. In my last OS install (since it was intended to be the last one for a while), I started installing all of the little utilities I’ve been wanting to play with. A couple of them (Sox? LAME? something to do with converting my CD’s to MP3 for my new MP3 player, anyway) wouldn’t compile with the Companion CD packages, and I had to go back to the sunfreeware.com packages. I guess I wasn’t all that clear in my previous post.—Rainer

This would be the qxml.cpp file, correct? Since Qt now compiles with thread support, I wonder if I need to do this. It wouldn’t hurt to try, I guess...—Rainer

I wonder if, as Sun moves further to Xorg, if the Xrender libraries and headers will start to show up (I’m assuming this is the RENDER you are referring to...). There is an xrender package on sunfreeware.com that you may want to take a look at.—Rainer