[SOLVED] Slackware -current and libunistring

tuxrules · 07-19-2017, 09:00 PM

Running -current and updated to the latest packages from today. I get this:

Code:

ldd /usr/bin/vte-2.91 | grep "not found"
Not found: libunistring.so.0

Code:

ldd /usr/bin/xfce4-terminal | grep "not found"
Not found: libunistring.so.0

I have libunistring installed. I can also manually link libunistring.so.2.0.0 to libunistring.so.0 but that won't be a solution. I've tried re-compiling both vte and xfce4-terminal using -current source but still missing shared library.

Thanks,

Didier Spaier · 07-19-2017, 10:19 PM

This symlink should have been made installing or upgrading to l/libunistring-0.9.7-x86_64-1.txz, released on Sat Jul 8 00:11:34 UTC 2017 according to the Current (pre-release) ChangeLog for x86_64.Yes, I see now in doinst.sh only:

Code:

( cd usr/lib ; rm -rf libunistring.so )
( cd usr/lib ; ln -sf libunistring.so.2.0.0 libunistring.so )
( cd usr/lib ; rm -rf libunistring.so.2 )
( cd usr/lib ; ln -sf libunistring.so.2.0.0 libunistring.so.2 )

PS Similar thread.

tuxrules · 07-20-2017, 07:26 AM

Thanks Didier Spaier, I had already checked doinst.sh and didn't see any links being created for libunistring.so.0. I had checked the thread you mentioned and manually linking as below works but I was looking for the actual cause of this. Perhaps other people running -current are not seeing this and I would like to know what I did differently.

Code:

ln -s /usr/lib64/libunistring.so.2.0.0 /usr/lib64/libunistring.so.0

I've been running slackpkg install-new, slackpkg upgrade-all and slackpkg clean-system with every -current update including scanning the changelog to make sure I'm not missing any important piece of information.

Thanks,

willysr · 07-20-2017, 08:11 AM

I got different results here:

Code:

ldd /usr/bin/xfce4-terminal | grep "not found"

returns 0 results, meaning it works just fine

Also there's no /usr/bin/vte-2.91

Toutatis · 07-20-2017, 08:13 AM

I have slackware64-current installed, but no /usr/bin/vte-2.91

ponce · 07-20-2017, 08:52 AM

Tuxrules, what does the following command outputs on your installation?

Code:

ls -la /var/log/packages/vte*

gmgf · 07-20-2017, 09:01 AM

it's normal /usr/bin/vte-2.91 is not include in slackware-current vte package, try to reinstall vte, and the new xfce4-terminal packages , probably that this would solved your problem

gmgf · 07-20-2017, 09:27 AM

this problem is probably due to a possible conflict under vte slackware-current package and another vte3 package present on SBO or other CSB and MSB.

tuxrules · 07-20-2017, 03:00 PM

Quote:

Originally Posted by gmgf

this problem is probably due to a possible conflict under vte slackware-current package and another vte3 package present on SBO or other CSB and MSB.

Thanks gmgf. vte-2.91 is part of vte3 SBo package. recompiled it and all is well now. Sorry should have looked closely but I somehow thought vte-2.91 was part of stock Slackware.

Thanks everyone!

willysr · 07-20-2017, 05:10 PM

yes, it's now part of Slackware, but under the name of vte instead of vte3 (I added vte3 into SBo because a lot of other packages requires that new version of vte, while Slackware is still using the old API at that time.

gmgf · 07-21-2017, 02:17 AM

If, you use vte3 SBO recompiled package, i think it's better to remove the slackware vte package