current - qt5 slackbuild error - icu4c wrong version
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.
current - qt5 slackbuild error - icu4c wrong version
I updated to the latest version of current today (2019/10/21). I tried to run pulseview but got an error. Last time this happened I had to run the slackbuild for qt5 from Ponce's repository and then the slackbuild for pulseview. This time I can't build qt5 because it wants icu4c version 64 and version 65 is installed in the latest version of current. I'm posting this in the hope that someone will resolve the mismatch. Thanks...Randy.
I think the easiest course of action would be to install Alien Bob's package plus dependencies that were recompiled for current or grab his build directory and build it, if you really need to build qt5. His slackbuilds are straightforward and documented.
Thanks for the replies. I'll look at rebuilding the prerequisites, although in the past (on occassion) I've had prerequisites that didn't have any prerequisites not build. If that happens I'll post the results. I may try Eric's qt5 package, although again I've had one of his packages not work for me. For now my workaround (which I admit is not good) was to install icu4c version 64....Randy
rest of slackbuilds needing qt5 , are tested with version under slackbuilds, good luck mixing , from 3rd repository qt5.
I use AlienBOB's qt5 and the bulk of my packages are built from SBo; which means if I'm building against qt5 I'm building against his QT5 package... and I never run into issues. I have run into small issues when on occasion AlienBOB's package falls a little behind current; but that very very very seldom ends up an issue for me; and this sort of thing should be expected when running -curent anyway.
I just checked the prerequisites for qt5 under current. The versions of the prerequisites I have installed are the same as the versions specified in Ponce's repository. To me it looks like there is a version mismatch between qt5 and the installed version of icu4c. I believe the version of icu4u was changed when I updated to the latest version of current today. I updated to the latest current Ponce repository after updating current....Randy
I ran into a icu4c mismatch earlier as well; using the QT5 package AlienBOB had up; but then AlienBOB "updated" his qt5 package / compiled it against the new icu4c and everything started to work again.
Last edited by khronosschoty; 10-21-2019 at 07:16 PM.
I just checked the prerequisites for qt5 under current. The versions of the prerequisites I have installed are the same as the versions specified in Ponce's repository. To me it looks like there is a version mismatch between qt5 and the installed version of icu4c. I believe the version of icu4u was changed when I updated to the latest version of current today. I updated to the latest current Ponce repository after updating current....Randy
I think that happens because you still have in your system something (stuff built from the unofficial SBo repository for current, other third-party packages, things built from sources, a previous qt5 package, whatever else...) that still links to the older icu4c libraries: I just built successfully again qt5 from this repository on a fresh and full installation of slackware64-current.
like I explain in the above topic I personally offer support only for clean and full installations of slackware64-current, but if you post some logs with the errors you got maybe someone can have a look and try to help you.
what may arise if you decide to use a newer qt5, like version 5.13.x that Alien Bob provides, is that, like USUARIONUEVO pointed above, you may encounter incompatibilities building other applications/libraries from this repository that uses it as a dependency: the stuff here is just forked from SBo, and there version 5.9.x is used.
this is not a problem if you need just qt5, but it may be if you need other stuff from here that needs it as a dependency.
Ponce, thanks for your reply. I appreciate the time and effort you put into this. I have been building exclusively from your repository. I realize things can get out of sync when current is a moving target and that packages will break. I'll be glad when 15.0 comes out and things stabilize again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.