LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-19-2017, 09:00 PM   #1
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,158

Rep: Reputation: 61
Slackware -current and libunistring


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,
 
Old 07-19-2017, 10:19 PM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,431

Rep: Reputation: Disabled
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.

Last edited by Didier Spaier; 07-20-2017 at 01:23 AM.
 
Old 07-20-2017, 07:26 AM   #3
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,158

Original Poster
Rep: Reputation: 61
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,
 
Old 07-20-2017, 08:11 AM   #4
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,170

Rep: Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396
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
 
Old 07-20-2017, 08:13 AM   #5
Toutatis
Member
 
Registered: Feb 2013
Posts: 269

Rep: Reputation: Disabled
I have slackware64-current installed, but no /usr/bin/vte-2.91
 
Old 07-20-2017, 08:52 AM   #6
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,523

Rep: Reputation: Disabled
Tuxrules, what does the following command outputs on your installation?
Code:
ls -la /var/log/packages/vte*
 
Old 07-20-2017, 09:01 AM   #7
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,802

Rep: Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713
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

Last edited by gmgf; 07-20-2017 at 09:11 AM.
 
Old 07-20-2017, 09:27 AM   #8
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,802

Rep: Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713Reputation: 713
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.

Last edited by gmgf; 07-20-2017 at 10:06 AM.
 
Old 07-20-2017, 03:00 PM   #9
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,158

Original Poster
Rep: Reputation: 61
Quote:
Originally Posted by gmgf View Post
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!
 
Old 07-20-2017, 05:10 PM   #10
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,170

Rep: Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396Reputation: 1396
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.
 
Old 07-21-2017, 02:17 AM   #11
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,802

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


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] can't load libunistring after latest current update slackb0t Slackware 2 07-09-2017 10:59 AM
Slackware ARM (current) epic mistake: the current Android kernels are kicked out! Darth Vader Slackware 16 08-25-2013 04:36 PM
[SOLVED] setup fails on most current Slackware-current March 26, 2012 AlleyTrotter Slackware 15 04-09-2012 06:05 AM
[SOLVED] Script to build always a current ISO image of Slackware (slackware-current) robertjinx Slackware 2 12-09-2010 02:00 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:56 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration