From: Mark K. <mk...@co...> - 2002-11-26 16:33:34
|
Hello all, I continue in my struggle to get Rosegarden to build. I hope I can get this out of the way today as I'll be leaving on a short 5-day vacation tomorrow and would like to have this behind me. Nothing much has changed, but I do have some more information. I hope it will help. 1) I've built RG (well, attempted to build) on two machines here in the office this morning, as well as one at home very early this morning. All three are RH 7.3, PlanetCCRMA. One runs fluxbox, the other two run KDE. All three builds failed. The build process is: a) rm rosegarden dir, rm /usr/share/apps/rosegarden, rm /usr/bin/rose* b) Complete CVS download c) make -f Makefile.cvs d) ./configure --with-qt-dir=/usr/lib/qt3 --prefix=/usr e) make f) make install 2) On the fluxbox machine I die at the make stage (e above) with the following errors: make[3]: Entering directory `/root/rosegarden/gui' /usr/lib/qt3/bin/uic -o rosegardentransport.h ./rosegardentransport.ui /usr/lib/qt3/bin/uic: relocation error: /usr/lib/qt3/bin/uic: undefined symbol: __ti15QGPluginManager make[3]: *** [rosegardentransport.h] Error 127 make[3]: Leaving directory `/root/rosegarden/gui' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/rosegarden/gui' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/rosegarden' make: *** [all] Error 2 [root@RH73WO rosegarden]# 3) On both of the KDE machines I fail with a dialog box that I sent to Guillaume last evening telling my that the installation contains the wrong version of Rosegarden. It also says "The wrong versions of Rosegarden's data files were found in the standard KDE installation directories. (I an 4-0.8, but the installed files are for version .)" While this appears to be similar to the error Miguel fixed yesterday, it is not fixed in my environments. 4) Guillaume sent me a perl command, which I cannot find at this second, that tested the VERSION. I ran that on two of the three machines. It printed 4-0.8, as expected, not '.' or anything that looked wrong. OK, I will keep plugging away, but after getting the same incorrect results on three machines, for me anyway, it's real. I look forward to getting this behind me. Mark |