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.
Now that you mention PyQt and since your name appears in the PyQt.SlackBuild, is it possible you could shepherd through a small fix please - regardless of version changes?
One of the products when PyQt.SlackBuild executes 'make' is a file named libpythonplugin.so (in the designer directory). However when 'make install DESTDIR=$PKG' is run, this file is installed directly into the host system rather than into $PKG. The reason is that libpythonplugin.so is built in a directory with python semantics and DESTDIR has no meaning - you can set it to anything you like but it will be ignored. Looking at the install_target in the designer directory's Makefile, you can see that it is looking for a definition of INSTALL_ROOT, not DESTDIR. Since INSTALL_ROOT is meaningless everywhere else, the simple fix which would restore libpythonplugin.so to the final package is to change the line
Code:
make install DESTDIR=$PKG || exit 1
to
Code:
make install DESTDIR=$PKG INSTALL_ROOT=$PKG || exit 1
The libpythonplugin.so file is what enables Qt Designer files to be recognized/used in a PyQt application. For those of us using Designer, it would be great to have this facility back without having to rebuild the package ourselves.
chris
Hi Chris
It seems like the library which gets added to the package is called libpyqt4.so (installed to /usr/lib64/qt/plugins/designer/libpyqt4.so) and not libpythonplugin.so. Correct? PyQt 4.11.3.
orc, mcelog, gnuplot, bash, git, swig, make, libcanberra, lm_sensors, procps-ng, tcl, tk, expect all queued up here, though at least make and procps-ng are questionable. We'll see what volkerdi has to say on those :-)
Re x11 stuff, I've got 1.17.x queued here, and I played around with libinput and xf86-input-libinput a bit. Those work fine here, it seems, but I'll admit to some uneasiness about using them due to the fact that they're so new. libepoxy seems fine and even desirable, as some stuff can use it with the Xpresent extension (in fact, xfwm4 git wants it), but I'm not at all convinced that libinput is a good decision right now. Those can be added to SBo for the next release if someone wants to use them.
It seems like the library which gets added to the package is called libpyqt4.so (installed to /usr/lib64/qt/plugins/designer/libpyqt4.so) and not libpythonplugin.so. Correct? PyQt 4.11.3.
Ah yes, it was named libpythonplugin.so in the current 14.1 & -current version (4.9.6). I just tried 4.11.3 (with sip-4.16.7) and found the name has changed to libpyqt4.so with the same problem of installing directly into the system, rather than $PKG. The same fix works though.
Thanks for the update Robby. Procsps-ng will be useful for JFS root, but I also forgot to mention we need to address the issue with Grub not detecting btrfs root partitions on GPT.
My Grub-2.02~beta2 package has a legacy mode detection patch specifically to fix that, but it's tuned for Grub-2.02~beta2 sources though.
Ah yes, it was named libpythonplugin.so in the current 14.1 & -current version (4.9.6). I just tried 4.11.3 (with sip-4.16.7) and found the name has changed to libpyqt4.so with the same problem of installing directly into the system, rather than $PKG. The same fix works though.
Thanks for your interest.
chris
The updated PyQt and the new PyQt5 packages I have built for my KDE 5 repository have the designer plugin included. I hope to release them in a couple of days (after I have rebuilt the whole of KDE 5 with new versions).
The updated PyQt and the new PyQt5 packages I have built for my KDE 5 repository have the designer plugin included. I hope to release them in a couple of days (after I have rebuilt the whole of KDE 5 with new versions).
gnu make - I've been using 4.1 for a few months on Slack64-14.1 with no issues. oprofile - I had problems compiling 0.97 with gcc-4.9.2 but oprofile-1.0.0 compiled with no issues. binutils which I found easier to download here. My reason for trying this is that 2.24.51.0.3 wouldn't compile with gcc-4.9.2. After upgrading to 2.25.51.0.1 I was then able to compile gcc-5.1.0 with a few small additions to the configure invocation in the SlackBuild.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.