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.
You stated "it was a slackbuild off your sight [sic]", without formally correcting yourself. Maybe it was lost in the way you type your responses, but it certainly wasn't obvious that you realized they were from different repos based on your post.
the main one was off of ponce that was not working was notepadqq that I was having issues with, then after I posted on it, then had some time so I read what was being posted and see others having the same issues with libhyphen.so then seen @willysrpost #1658 where is said, "try installing hyphen". so I did that too, and it worked and I just added too much post information on the situation (obviously) with a question on the version numbers, that was not meant to put others into a tail spin. it was just a yes or no rhetorical question, because 5.11.3 is larger than 5.3. Just showing my results is all. then thinking that "hyphen" maybe should be put into the list of deps for that package, but not commenting on that thought.
I just kept adding more information in lue of using more post to do it to show what was really going on with my system, and not pointing fingers at anyone it was mainly about the libhyphen.so not being in there and nothing about it being a dep that I seen. Sorry for all of the confusion....
Just showing my results is all. then thinking that "hyphen" maybe should be put into the list of deps for that package, but not commenting on that thought.
hyphen is not a dependency of Notepadqq. It's only an issue for you because you are using Alien Bob's Qt5 (or maybe qt5-webkit), which he linked against hyphen.
hyphen is not a dependency of Notepadqq. It's only an issue for you because you are using Alien Bob's Qt5 (or maybe qt5-webkit), which he linked against hyphen.
now you know way I didn't say anything on that, not knowing the behind the scenes on that deps. anyways notpadqq does work. please lets move on to other issues of the day...
looks like PyMOL-2.2.0 while working fine on 14.2 is not compatible with the newer mesa in current, but the newer PyMOL-2.3.0 (that needs the additional dependency mmtf-cpp) seems to work fine on this platform: as this introduces a new dependency (also if it's just a bunch of headers files) it's better if you ask the maintainer to update it also on stable.
libgusb currently fails to build on multilib-enabled systems on current.
This is because it erroneously tries to build against a library located at /usr/lib/gobject-introspection/giscanner/_giscanner.so, which is 32-bit.
It does this because it calls a script located at /usr/bin/g-ir-scanner which first looks to /usr/bin/../lib/gobject-introspection, and the key is "lib" is hardcoded as the first test match. Since it matches, it then goes on to try to utilize the 32-bit version on multilib.
latest version 1.59.x has this issue fixed as well
Are you sure? I looked at the source for the 'master' branch before submitting the patch and it seemed unchanged from 1.58.x. I'll double-check when I have some more time.
EDIT - Oh yes, I see. They resolved it in another way. Guess my poor, lonely patch won't be needed after all
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.