LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Problems with QT compat32 in Slackware64 (http://www.linuxquestions.org/questions/slackware-14/problems-with-qt-compat32-in-slackware64-751334/)

Daedra 08-30-2009 05:44 PM

Problems with QT compat32 in Slackware64
 
This problem is similar to the one I posted earlier except this one isn't fixing itself ;). Whenever I try to compile a program that is dependent on QT I keep getting warning like this.

CMake Warning at /usr/share/apps/cmake/modules/KDE4Macros.cmake:561 (add_library):
Cannot generate a safe runtime search path for target plasma_applet_cwp
because there is a cycle in the constraint graph:

dir 0 is [/usr/lib/qt/lib]
dir 1 must precede it due to runtime library [libQtSvg.so.4]
dir 1 is [/usr/lib64/qt/lib]
dir 0 must precede it due to runtime library [libQtXml.so.4]

Some of these libraries may not be found correctly.
Call Stack (most recent call first):
CMakeLists.txt:21 (kde4_add_plugin)

I understand what this warning means, It basically saying its looking at /usr/lib/ first and then /usr/lib64 second? I know that is not right and that is why I am getting compile errors. How do I tell the buildscript to ignore /usr/lib and look in /usr/lib64. I am not to familiar yet with cmake so I dont know if its a line I could pass it fix this or not.

Thanks

mlangdn 08-30-2009 05:56 PM

See if this can help. It gives an example of how to tell cmake where something is:

http://www.cmake.org/Wiki/CMake_HowT...talledSoftware

This may be of use also:

http://www.cmake.org/Wiki/CMake_Useful_Variables

Daedra 08-31-2009 05:32 AM

Ok so I am going to read that as my next step, but I just got Slackware64 reinstalled. I decided to uninstall the qt compat32 library and I got a new error about missing qmake, I then uninstalled the 64bit qt package and reinstalled and my system broke, having missing errors about libQt4.foo errors. I am so close this is the last hurddle I have to get over before my system is multilib. I cant figure what I am doing wrong.

Daedra 08-31-2009 04:56 PM

Ok so I think I fixed it, I don't know how it got fixed which bothers me, but here is what I did. After I install the QT-compat32 package that I made using AlienBob's wiki I started having the above error when ever I tried to compile a program dependent on QT4. I then tried reinstalled QT4 64bit package using upgradepkg --reinstall which then fixed my problems. This leads me to believe that something got over written which was causing these errors and a reinstall put things back in place. Can anyone out there at least confirm this error for me, or is it just me, lol.

Thanks

Alien Bob 08-31-2009 06:44 PM

Thanks for checking this Daedra, I see now what is wrong with the qt-compat32 package.

I will fix the convertpkg-compat32 script so that it will properly deal with the 32bit qt package. Indeed, "upgrade --reinstall" of the original 64bit qt package will fix several symbolic links that are were erroneously created in /usr/bin by the qt-compat32 package.

Eric

EDIT: I uploaded a fixed compat32-tools package along with a refreshed set of actual -compat32 packages (for those who don't have a local 32bit Slackware tree). This time, the qt-compat32 package behaves.

forum1793 08-31-2009 09:15 PM

Will this allow the previous version of mythtv to work? It doesn't support qt4.

Alien Bob 09-01-2009 03:20 AM

Qt4 has nothing to do with 32bit compatibility. If you want to run mythtv on Slackware64 and need Qt3 for that, then you should install the packages in the /extra/kde3-compat directory of your Slackware64 DVD. There is a Qt3 package there which you can install without fear of overwriting the Qt4 stuff.
I see no need to install 32bit multilib support just for mythtv.

Eric

forum1793 09-04-2009 09:03 PM

I didn't ask for multilib stuff. Just asked if myth now worked.

Edit: This observation with slackware-13.0 32 bit.

I loaded up all packages in kde3-compat directory and tried mythtv.

No go.

Got following:

Code:

mythtv-setup: error while loading shared libraries: libqt-mt.so.3: cannot open shared object file: No such file or directory
I'll play with this a bit. I loaded myth stuff before the kde3 stuff. Maybe with kde3compat I can use slackbuild script and get something. Either way next myth version will probably support qt4.

I don't necessarily like mythtv that much but it does work. I'd be just as happy getting something that doesn't use the mysql stuff anyway.

Alien Bob 09-05-2009 07:29 AM

Quote:

Originally Posted by forum1793 (Post 3670377)
I didn't ask for multilib stuff. Just asked if myth now worked.

Edit: This observation with slackware-13.0 32 bit.

Then don't hi-jack a thread that deals about multilib in Slackware64...

Eric

rup1033 09-09-2009 03:24 PM

Also having the same issue.
 
I get this in my error when trying to compile SMB4K(64bit):
dir 0 is [/usr/lib/qt/lib]
dir 1 must precede it due to runtime library [libQtDBus.so.4]
dir 1 is [/usr/lib64/qt/lib]
dir 0 must precede it due to runtime library [libQtCore.so.4]

Some of these libraries may not be found correctly.

How can I go about fixing this so that it will compile. I have multi-lib installed by following the quick and dirty steps to getting multi-lib going by installing the base packages + tools then doing the mass-convert script to get the -compat32 base set of software and installed that. I saw that you suggested reinstalling qt fromt he slackware dvd which I did installpkg qt*.txz(from slackware dvd /l directory), it installed but it did not seem to fix the issue by restoring said symlinks etc.
Any help is appreciated, thanks.

ponce 09-09-2009 04:39 PM

compiled smb4k now on multilib system with this slackbuild and these sources (a cvs tarball): if you want to try it package is here :)


All times are GMT -5. The time now is 06:29 AM.