Error updating SEQ..

[TWRabat]

Im pretty new to this, i had a friend of mine over and he's stumped now by this..

Lemme give some background. The box is a Dual PPro 200 Compaq proliant box. Running Redhat 8.

We tried updating the version of SEQ by running the seq.txt file, when it went into make everything, it died at the qt query. Said we needed 2.3.2n when i was running 2.3.1.

Ok, so we got the RPM, that had problems installing, but we got 2.3.2 in, right? So we redid the install, now its posting this:

warning: qt-devel-3.0.5-7.i686.rpm: V3 DSA signature: NOKEY, key ID f9651d5a
error: Failed dependencies:
libstdc++.so.2.10 is needed by qt-devel-3.0.5-7
qt2-devel conflicts with qt-devel-3.0.5-7
qt-devel = 1:3.0.5-17 is needed by (installed) qt-designer-3.0.5-17


Were stumped now, any help or hints?

[Cryonic]

Yes... WE DON'T SUPPORT USING A SHELL SCRIPT TO UPDATE/INSTALL SHOWEQ.

There are plenty of guod guides that show you how to do it. Find one, read it, read it again, now really read it. Ok, now try to install SEQ following those steps that you read.

[TWRabat]

The shell scrip provided in post http://seq.sourceforge.net/showthrea...ownload+showeq
Seemd to work, and was actualy instructed by the documentation to use, was the one provided. Its set for Redhat 7.2, but seemd to work the first time around. If it was posted, why is it not supported..?

[high_jeeves]

The author of that script may support it, the seq community does not. You use any 3rd party script at your own risk.

--Jeeves

[Mr. Suspicious]

and was actualy instructed by the documentation to use, was the one provided

Exactly what FILE in your showeq directory (the official documentation) does recommend this?

[NHRAfan]

If you are running RH 8.0 then you are making more work for yourself by trying to use qt 2.3.2. Go back and make sure that you have installed ALL of the developer packages for X, Gnome, and KDE then go back and use ./configure --without-qt-validation.

This will allow you to use qt 3.0.5 which comes with RH 8.0 and save you the trouble of getting 2.3.2 to work for you.

[Cryonic]

only problem with using 3.05 is that SEQ has problems with it. Hence the continued recommendation to use 2.3.2.

[NHRAfan]

/em puts on FR gear

I have only been using SEQ for a few days now, what kind of problems is SEQ having with 3.0.5? Once I worked through the normal n00b mistakes my SEQ has worked just fine.

[Dedpoet]

Do a search on "3.0.5". Poor performance, lockups during decode (not so much of an issue with a key sniffer), disappearing map lines, and font issues are just some of the problems people have had. 3.0.x will work, but most find it to work much nicer with 2.3.2.