SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is this on Slackware 14.2_64_multilib like it's noted on your profile?
There might be qt4 on that system, what it probably did well, it found qmake-qt4 instead of qmake-qt5
Try to temporarily remove qmake-qt4 if possible, it might help the program compile.
But I can't guarantee, because the smplayer I use is still like version 17.12 haven't tried the new one.
Here on 15.0 without multilib, I only have these, one symlink and one binary;
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 458
Rep:
This comes up every once in a while with Qt stuff; try running the SlackBuild from root's login shell (with "su -"). Non-login shells don't have the Qt directory on the path by default.
Is this on Slackware 14.2_64_multilib like it's noted on your profile?
Hi elcore,
I am afraid not, this is slack-15 I am having a little difficulty with; I am setting up slack-15, but still using 14.2.
Hi pghvlaans,
Quote:
This comes up every once in a while with Qt stuff; try running the SlackBuild from root's login shell (with "su -"). Non-login shells don't have the Qt directory on the path by default.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.