Gentoo, gcc 3.1, qt 3.0.4, and seq
Hey all. I just wanted to share my experience with setting up seq with the configuration in the title. I don't want to call this a "guide" since it's not step-by-step and seq is not supported under qt 3.x right now, which is why this is not in the help section. I just wanted to play because I'm a geek and that is what we do.
I set up Gentoo and did my entire stage 1 build with gcc 3.1 using the standard setup guide (www.gentoo.org) and this guide. For those who have never done this, note that it takes several hours, even on a fast system. I am doing all of this on a 1.13 GHz P3 laptop with 256 meg RAM. The next step was building X, which also takes several hours. The consensus on the Gentoo forums is that compiles take longer with gcc 3.1, but performance is better in the end.
Once I had a working X (a couple more hours) I emerged qt 3.0.4. I didn't do it all at once, because I wanted to apply the patch that Zaphod mentioned here. I just did the unpack first, applied the patch, then did the compile, install, and qmerge. 3.0.4 took significanly longer to compile than 2.3.2 under gcc 3.0 - I was at lunch when it finished, but I'm guessing a little under 2 hours.
I retrieved and built seq in the normal way. The only thing different is at the end of the configure, it reports, "Workable {???} Seq is not supported under qt 3.0" or something similar. The build went fine though, but took about 7 minutes as opposed to the 4 minutes it would take before.
I ran seq first under twm, and I got the following warnings when starting it up, but they did not seem to cause any serious problems:
Code:
QObject::connect: Incompatible sender/receiver arguments
QSignal::signal(const QVariant&&) --> MapMenu::toggle_spawnPoints(int)
QObject::connect: Incompatible sender/receiver arguments
QSignal::signal(const QVariant&&) --> EQInterface::set_interface_Font(int)
QObject::connect: Incompatible sender/receiver arguments
QSignal::signal(const QVariant&&) --> EQInterface::set_interface_statusbar_Font(int)
QObject::connect: Incompatible sender/receiver arguments
QSignal::signal(const QVariant&&) --> EQInterface::toggle_interface_SavePosition(int)
QObject::connect: Incompatible sender/receiver arguments
QSignal::signal(const QVariant&&) --> EQInterface::toggle_interface_UseWindowPos(int)
QObject::connect: Incompatible sender/receiver arguments
QSignal::signal(const QVariant&&) --> EQInterface::toggle_interface_UseStdout(int)
QObject::connect: Incompatible sender/receiver arguments
QSignal::signal(const QVariant&&) --> EQInterface::toggle_interface_NoBank(int)
QObject::connect: Incompatible sender/receiver arguments
QSignal::signal(const QVariant&&) --> EQInterface::select_interface_FormatFile(int)
Performance was "quirky" under twm, but I haven't eliminated bad ATi Radeon drivers as a possible cause yet. Processor usage was all over the chart and seemed to be very dependant upon size of the main window. It ran great in small windows, but as I increased the size, X started taking as much as 90% of the processor. I am going to play with the gatos drivers this weekend, which makes me nervous because I hosed my install with them once.
To eliminate the window manager variable, I installed fluxbox and had the same issues. I haven't tried kde yet because I haven't had the 4 hours to build it.
I'm going to start eliminating variables this weekend - first try kde, then gatos drivers. My suspicion is that the drivers will help the performance issue and kde won't make a difference. If both of those fail to help, I will build against qt 2.3.2 and try that.
I hope this helps someone in some way. Doing something like this is a great way to learn vast amounts about Linux, and it has been fun for me. I'll update this post after I try a few more things over the next few days.
-Dedpoet
[edited for a typo]
