Hi, I'm very eager to try fmit to tune my 'tiple' a traditional colombian instrument with 12 strings in 4 orders, but I'm stuck like Jan Depner at: make[2]: Entering directory `/home/andres/Old/fmit-0.9.9/ui' /usr/lib/qt-3.3.3/bin/uic ConfigForm.ui > ConfigForm.h /usr/lib/qt-3.3.3/bin/uic -impl ConfigForm.h ConfigForm.ui > ConfigForm.cpp /usr/lib/qt-3.3.3/bin/uic: relocation error: /usr/lib/qt-3.3.3/bin/uic: undefined symbol: _ZNK7QString3argExii make[2]: *** [ConfigForm.cpp] Error 127 I'm using Planet CCRMA FC1.

Apparently the qt 3.3.3 rpms from CCRMA don't replace qt.sh and qt.csh in /etc/profile.d. I hand edited the scripts and replaced the default 3.1 with 3.3.3. I also had to remove qt3.1 from /etc/ld.so.conf and run ldconfig.

This got me past the previous error but, unfortunately, I now end up with: ../ui/ConfigForm.cpp:235:14: warning: no newline at end of file ../ui/ConfigForm.cpp:235: error: syntax error at end of input make[2]: *** [ConfigForm.o] Error 1 make[2]: Leaving directory `/data2/sound2/fmit-0.9.9/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/data2/sound2/fmit-0.9.9' make: *** [all] Error 2 That file appears to be truncated.

On Sat, 2005-01-08 at 21:54, Fernando Lopez-Lezcano wrote: > On Sat, 2005-01-08 at 18:05, Andres Cabrera wrote: > > Hi, > > I'm very eager to try fmit to tune my 'tiple' a traditional colombian > > instrument with 12 strings in 4 orders, but I'm stuck like Jan Depner at: > > > > make[2]: Entering directory `/home/andres/Old/fmit-0.9.9/ui' > > /usr/lib/qt-3.3.3/bin/uic ConfigForm.ui > ConfigForm.h > > /usr/lib/qt-3.3.3/bin/uic -impl ConfigForm.h ConfigForm.ui > ConfigForm.cpp > > /usr/lib/qt-3.3.3/bin/uic: relocation error: /usr/lib/qt-3.3.3/bin/uic: > > undefined symbol: _ZNK7QString3argExii > > make[2]: *** [ConfigForm.cpp] Error 127 > > > > I'm using Planet CCRMA FC1. > > Does it build with the original qt in fc1? (qt-3.1, I think). That would > be a better option. > > If it really needs qt 3.3 and you are using the qt33 package then you > need to set a couple of environment variables while building, QTDIR (set > to /usr/lib/qt-3.3.3) and LD_LIBRARY_PATH (set to > /usr/lib/qt-3.3.3/lib), this last one should fix the relocation error. > You also will have to set LD_LIBRARY_PATH when running the binary. >

Thanks Fernando, That does it! I now have fmit.Will start testing right away. There was this funky message: Making all in tr make[2]: Entering directory `/home/andres/New/fmit-0.9.9/tr' lupdate -verbose ../src/*.cpp ../src/*.h ../ui/*.ui -ts fmit_fr.ts /bin/sh: line 1: lupdate: command not found make[2]: *** [fmit_fr.qm] Error 127 make[2]: Leaving directory `/home/andres/New/fmit-0.9.9/tr' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/andres/New/fmit-0.9.9' make: *** [all] Error 2 But the executable was still produced, and runs OK!

Fernando Lopez-Lezcano wrote: >On Sat, 2005-01-08 at 20:46, Jan Depner wrote: >>Apparently the qt 3.3.3 rpms from CCRMA don't replace qt.sh and qt.csh >>in /etc/profile.d. I hand edited the scripts and replaced the default >>3.1 with 3.3.3. I also had to remove qt3.1 from /etc/ld.so.conf and run >>ldconfig. > >Well, you can do that, but that will mess up all qt applications that >were not linked against qt3.3 (that is, all qt apps that were originally >compiled for qt3.1). Probably not what you want. Both libraries are >_not_ compatible and that is why qt33 does not replace qt3.1, it is >designed to be installed together with it. > >For things to work you do have to use the environmental variables and/or >the -rpath linker option when you compile against qt33. > >> This got me past the previous error but, unfortunately, I now >>end up with: >> >>../ui/ConfigForm.cpp:235:14: warning: no newline at end of file >>../ui/ConfigForm.cpp:235: error: syntax error at end of input >>make[2]: *** [ConfigForm.o] Error 1 >>make[2]: Leaving directory `/data2/sound2/fmit-0.9.9/src' >>make[1]: *** [all-recursive] Error 1 >>make[1]: Leaving directory `/data2/sound2/fmit-0.9.9' >>make: *** [all] Error 2 >> >>That file appears to be truncated. > >I don't know about this one, I have not used qt33 that much (qmidiarp >and muse so far, I think) and in both cases it worked fine. > > >>On Sat, 2005-01-08 at 21:54, Fernando Lopez-Lezcano wrote: >>>On Sat, 2005-01-08 at 18:05, Andres Cabrera wrote: >>> >>>>Hi, >>>>I'm very eager to try fmit to tune my 'tiple' a traditional colombian >>>>instrument with 12 strings in 4 orders, but I'm stuck like Jan Depner at: >>>> >>>>make[2]: Entering directory `/home/andres/Old/fmit-0.9.9/ui' >>>>/usr/lib/qt-3.3.3/bin/uic ConfigForm.ui > ConfigForm.h >>>>/usr/lib/qt-3.3.3/bin/uic -impl ConfigForm.h ConfigForm.ui > ConfigForm.cpp >>>>/usr/lib/qt-3.3.3/bin/uic: relocation error: /usr/lib/qt-3.3.3/bin/uic: >>>>undefined symbol: _ZNK7QString3argExii >>>>make[2]: *** [ConfigForm.cpp] Error 127 >>>> >>>>I'm using Planet CCRMA FC1. >>>> >>>> >>>Does it build with the original qt in fc1? (qt-3.1, I think). That would >>>be a better option. >>> >>>If it really needs qt 3.3 and you are using the qt33 package then you >>>need to set a couple of environment variables while building, QTDIR (set >>>to /usr/lib/qt-3.3.3) and LD_LIBRARY_PATH (set to >>>/usr/lib/qt-3.3.3/lib), this last one should fix the relocation error. >>>You also will have to set LD_LIBRARY_PATH when running the binary. >>>

On Sat, 2005-01-08 at 20:46, Jan Depner wrote: Well, you can do that, but that will mess up all qt applications that were not linked against qt3.3 (that is, all qt apps that were originally compiled for qt3.1). Probably not what you want. Both libraries are _not_ compatible and that is why qt33 does not replace qt3.1, it is designed to be installed together with it.

On Sun, 2005-01-09 at 07:58, Jan Depner wrote: Interesting. The original qt included in fc1 is qt 3.1.2-14. All qt apps included in fc1 are dynamically linked (and were compiled) against this version. The multithreaded dynamic libraries are (in this version): libqt-mt.so.3.1.2 (3.1.1 in rh9) For qt version 3.3.3 the version is: libqt-mt.so.3.3.3 I originally tried to just upgrade the qt packages instead of creating a new, different package. When I tried installing qt 3.3.3 as an rpm upgrade, rpm itself complained about broken dependencies (ie: the new qt would not work with older applications according to rpm - I don't remember what were the missing dependencies). I've done a little bit of research and I think the problem was not in the qt library itself but in some additional libraries that were part of the package (I'm not a qt expert so I don't know what they are). In qt 3.1.x some apps depend not only on qt-*.so but also on libqtassistantclient.so, which is not present in my qt 3.3 builds. I can't be completely sure without rebuilding everything but most probably that was the dependency that was not allowing a clean upgrade from qt 3.1 to qt 3.3 (current apps I have in rh9 that depend on that include qt-designer - of course - but also PyQt, kaconnect, qjackconnect, qarecord, qamix and ams). Hmm, all apps done by the same author, maybe it is a build problem and that library is not really necessary? Or maybe just a packaging problem? On rh9 there is also a direct dependency by redhat-artwork on /usr/lib/qt-3.1, that's probably because the bluecurve theme is not included in the qt package but rather in the redhat-artwork package. I included the bluecurve stuff in qt33 explicitly. Most probably you don't have apps that depend on libqassistantclient (or you have not tried to run them) and that is why you don't have any problems.