SBo scripts not building on current (read 1st post, pls)
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.
but yes, we are inclined to remove webkitgtk{,3} and whatever still depends on it from SBo.
Thanks much for the patch. It worked, but gnucash-legacy (version 2.6.21) no longer starts, with a message 'ERROR: Unbound variable: eval-when' when I start it in a terminal window. Given its age, I believe it is time to remove gnucash-legacy and gnucash-legacy-docs from SBo. Thanks again for your help.
davfs2 seems to not like the newer version of neon in -current
Code:
checking linking against neon... yes
configure: incompatible neon library version 0.31.2: wanted 0.27 28 29 30
configure: error: could not find neon
system/davfs2: davfs2.SlackBuild failed (status 1)
just version-bump davfs2 to version 1.6.0.
Quote:
would this be something that has to go back to the package maintainer to build a new version of davfs2?
if we are during the normal lifetime of stable and current the maintainer is not supposed to use current so we usually avoid them the burden to maintain script for the development version of Slackware and I collect patches in the unofficial for of the SBo repository.
in this specific moment, as submission are closed and we are working on the master branch on SBo to make all the script we can compatible with current (to be ready whenever 15.0 will be released), this kind of fix to let stuff build on current are still ok if reported here.
in any case, if the maintainer wish to handle things differently and/or has a better fix, I have no problem in pushing his stuff instead of the fixes I found.
I have compiled them on the latest Slackware current. My KDE4 port is compiling with them.
I have split the original qt package which included qtwebkit (which depends on qt).
qtwebkit can now compile without being removed. qtwebkit is also necessary for a lot of kde4 packages.
I have keep the original name of qt because new packages for qt5 have the 5 in their name and I don't like renaming packages. But if there is some preferences for a renaming I will do it.
Hi BrunoLafleur,
I had a look at this an adapted the script so they could be pushed on SBo: I was able to build qt with those but unfortunately qtwebkit won't build...
you're right, my bad: when I was amending the SlackBuild I copied the SLACKFLAGS block from one SlackBuild to the other.
I fixed the SlackBuild with the flags you suggest and uploaded it in the same directory
but having installed the resulting qt and qtwebkit on my test virtual machine I noted a thing that should be somehow handled: the qt package install an /usr/bin/qmake symlink and an /usr/lib64/qt/bin/qmake that override in $PATH the /usr/lib64/qt5/bin/qmake needed by apps using qt5.
is it possible to rename those two to qmake-qt4 and use them in the build scripts so that it won't overlap with qt5 in Slackware current?
you're right, my bad: when I was amending the SlackBuild I copied the SLACKFLAGS block from one SlackBuild to the other.
I fixed the SlackBuild with the flags you suggest and uploaded it in the same directory
but having installed the resulting qt and qtwebkit on my test virtual machine I noted a thing that should be somehow handled: the qt package install an /usr/bin/qmake symlink and an /usr/lib64/qt/bin/qmake that override in $PATH the /usr/lib64/qt5/bin/qmake needed by apps using qt5.
is it possible to rename those two to qmake-qt4 and use them in the build scripts so that it won't overlap with qt5 in Slackware current?
Yes I think I can do that. But I need to test for dependencies in compilation dependencies. Anyway it is useful to do that.
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 451
Rep:
Hi, Ponce. fcitx-mozc failed to build in -current because pkg-config was looking for qt4-related packages. Applying the attached patch to the SlackBuild in your repo resulted in a successful build by disabling qt. Everything still looks normal on Plasma.
Hi, Ponce. fcitx-mozc failed to build in -current because pkg-config was looking for qt4-related packages. Applying the attached patch to the SlackBuild in your repo resulted in a successful build by disabling qt. Everything still looks normal on Plasma.
hi pghvlaans, I tried building with qt disabled and yes, it actually went fine, but I saw that newer versions could also support qt5: as you seem to use this, if you are interested, can you please get in touch with the maintainer asking for an update?
can you please also send me via pm a name and an email address to add them to the git commit?
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 451
Rep:
I don't think I've made enough posts to send private messages. "pghvlaans" is also my github name, and it's how I show up on my own SlackBuilds in any case.
OK, I'll try sending him an email about a version update tomorrow.
On last December, I created fcitx-mozc-2.26.4220.102.1 for my personal use purpose.
Because I wanted to use fcitx-mocz with Japanese new era(REIWA) support.
The version 2.26.4220.102.1 has already been applied Japanese new era patch.
Created package is working fine now on my personal slackware64-current environment.
Quote:
Originally Posted by ponce
hi pghvlaans, I tried building with qt disabled and yes, it actually went fine, but I saw that newer versions could also support qt5: as you seem to use this, if you are interested, can you please get in touch with the maintainer asking for an update?
can you please also send me via pm a name and an email address to add them to the git commit?
Since I am not familiar with script writing, my script is ugly (not smart). The script gets required sources one by one with wget command.
Anyway, I confirmed the script works on slackware64-current (gcc-10.3.0, glibc-2.33, python-3.9.4).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.