Search:

Dual PIII 1Ghz running your standard redhat system. Without enabling dual processor mode, takes about 30-40 minutes. Adding the -j3? (forgot offhand), takes about 10-15 min.

OH!! Now that menu item makes sense. :) Always wondered what that was for. :)

I searched the forums for "reversed location" and "backward location" and didn't come up with anything useful, so I'm assuming here that this is a new problem.

When you roll the mouse over...

I had the same problem. cvs updated, make clean, make, then make install.

After I noticed the issues and not seeing anyone else with the problem, I simply deleted the source, rechecked out...

Thanks tons for the update! But really most of all, thanks tons that I don't have to sniff through alot of "Even though the status is red, I can't get it to work!"

Kudos!

I did a search on donation and couldn't find the information needed to become a contributing member. I remember seeing this information once on the old ui, but I'm a bit lost on the new site...

Based on Eggman's instructions, I've fiddled with it to make it more understandable (well at least to me) and thought to share it with you.

Thanks all for the help and replies to make this happen....

Nevermind. I deleted the project and started from scratch. That seemed to have fixed it.

I assume running make makedist and configure again doesn't reset some files.

Anyway, I'm all good.

I can get the latest code to compile (with warning about using QT 3.x+)

I've follow your instructions but get compile problem in SEQ.

Only thing I can see different is that I'm using QT 3.1.1....

Because the new build requires to compile with the QT libraries again, you need to make sure your environment variables are set.

export QTDIR=/opt/qt-gcc3-2.3.2
export PATH=$QTDIR/bin:$PATH ...

You're right. I forgot to source my environments. Idiot here. <gets ready for that promised flame> :)

I haven't seen any threads on this, so I'm assuming this is new.

I cvs updated to the latest version of SEQ and tried to compile like I always did, but this time, I'm getting massive errors in...