Proprietary binary broke after an update in Slackware64-14.2
by FlinchX from LinuxQuestions.org on (#53VTH)
Just to avoid any confusion due to an eventual unfortunate wording: the topic means the update of said proprietary binary rather than Slackware update.
I've been using a proprietary binary for some time and today it got updated and failed to run.
The error is:
Code:error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directorySlackware64-14.2 doesn't have such a file.
I searched online and learned that this is related to ncurses. The fix suggested here https://forums.opensuse.org/showthre...-libtinfo-so-5 got the thing working again.
I had a look at slackware/slackware64-14.2/source/l/ncurses/ncurses.SlackBuild and I saw nothing related to libtinfo.
While I got my proprietary binary working after the aforementioned manual intervention, I have two questions:
1. Is it too much to expect that Pat will fix the ncurses package for 14.2 to create said symlink? Or are there any technical reasons why it wasn't done on purpose?
2. While I'm not using -current, I also had a look at the ncurses SlackBuild there. It has some libtinfo related explicit content, so I assume the symlink hack won't be needed there. But I'm also noticing that -current uses a newer major version of ncurses. It is very likely that the proprietary binary I'm using will keep linking against ncurses 5 even after the Slackware 15.0 release, which has ncurses 6. What's my plan for that future situation then? Or there will be a legacy ncurses 5 build on SBo maybe, that could be installed alongside, like there's one now for libpng?
I've been using a proprietary binary for some time and today it got updated and failed to run.
The error is:
Code:error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directorySlackware64-14.2 doesn't have such a file.
I searched online and learned that this is related to ncurses. The fix suggested here https://forums.opensuse.org/showthre...-libtinfo-so-5 got the thing working again.
I had a look at slackware/slackware64-14.2/source/l/ncurses/ncurses.SlackBuild and I saw nothing related to libtinfo.
While I got my proprietary binary working after the aforementioned manual intervention, I have two questions:
1. Is it too much to expect that Pat will fix the ncurses package for 14.2 to create said symlink? Or are there any technical reasons why it wasn't done on purpose?
2. While I'm not using -current, I also had a look at the ncurses SlackBuild there. It has some libtinfo related explicit content, so I assume the symlink hack won't be needed there. But I'm also noticing that -current uses a newer major version of ncurses. It is very likely that the proprietary binary I'm using will keep linking against ncurses 5 even after the Slackware 15.0 release, which has ncurses 6. What's my plan for that future situation then? Or there will be a legacy ncurses 5 build on SBo maybe, that could be installed alongside, like there's one now for libpng?