LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-30-2009, 04:44 PM   #1
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-15.0
Posts: 2,691

Rep: Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377
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
 
Old 08-30-2009, 04:56 PM   #2
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,845

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
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

Last edited by mlangdn; 08-30-2009 at 04:58 PM.
 
Old 08-31-2009, 04:32 AM   #3
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-15.0
Posts: 2,691

Original Poster
Rep: Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377
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.

Last edited by Daedra; 08-31-2009 at 05:28 AM.
 
Old 08-31-2009, 03:56 PM   #4
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-15.0
Posts: 2,691

Original Poster
Rep: Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377Reputation: 1377
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
 
Old 08-31-2009, 05:44 PM   #5
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
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.

Last edited by Alien Bob; 08-31-2009 at 06:20 PM.
 
Old 08-31-2009, 08:15 PM   #6
forum1793
Member
 
Registered: May 2008
Posts: 312

Rep: Reputation: 34
Will this allow the previous version of mythtv to work? It doesn't support qt4.
 
Old 09-01-2009, 02:20 AM   #7
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
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
 
Old 09-04-2009, 08:03 PM   #8
forum1793
Member
 
Registered: May 2008
Posts: 312

Rep: Reputation: 34
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.

Last edited by forum1793; 09-04-2009 at 08:05 PM.
 
Old 09-05-2009, 06:29 AM   #9
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
Quote:
Originally Posted by forum1793 View Post
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
 
Old 09-09-2009, 02:24 PM   #10
rup1033
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware
Posts: 2

Rep: Reputation: 0
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.
 
Old 09-09-2009, 03:39 PM   #11
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,105

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


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Video Problems in VirtualBox on Slackware64-current TSquaredF Slackware 8 10-20-2009 11:44 PM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM
Thank you for Slackware64 BCarey Slackware 3 08-17-2009 04:17 PM
[SOLVED] Slackware64-C client wont detect Slackware64-C Samba server slackass Slackware 5 08-07-2009 11:23 PM
asciidoc + docbook problems on slackware64-current Ron Parker Slackware 2 07-17-2009 01:29 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:32 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration