[SOLVED] chromium-dev installation of alien-bob failing on slackware-current with error
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.
Works fine here.
How "current" is your Slackware64-current? The GLIBCXX_3.4.20 is contained in the libstdc++.so.6 library version of gcc (gcc-g++-4.9.2-x86_64-3) which is part of Slackware64-current. It is also present in the multilib version of the gcc package (gcc-g++-4.9.2_multilib-x86_64-3alien).
What gives:
Code:
ls -la /usr/lib64/libstdc++.so.6*
ls -la /var/log/packages/gcc*
ls -la /var/log/packages/glibc*
though works fine grabbing the key from the slackware-current mirror
i had done a full system upgrade recently say a week back and my kernel had got updated too....from 3.10.7 or say to 3.18.11 specifically....
had blacklisted alien packages and slackbuilds but forgot to blacklist my kernel....
as a result my kernel had got upgraded.....
...should i post a new thread on this new issue?
Last edited by nitecrawler; 08-12-2015 at 11:33 PM.
finally, i was about to move to slackware 14.1 when i gave one last try with slackpkg update....
not only did i get my old customized system back but also chromium-dev from alien bob current is working fine...
sorry for the alarm mate...
CHROMIUM-DEV works just perfect....and i am posting this from chromium dev version current...
i ran the commands again just to confirm...below are the results
Code:
nitecrawler in ~ @ 19:18:31 $ ls -la /usr/lib64/libstdc++.so.6*
lrwxrwxrwx 1 root root 19 Aug 13 18:47 /usr/lib64/libstdc++.so.6 -> libstdc++.so.6.0.20
-rwxr-xr-x 1 root root 970768 Oct 21 2013 /usr/lib64/libstdc++.so.6.0.18
-rwxr-xr-x 1 root root 1003520 Aug 4 00:16 /usr/lib64/libstdc++.so.6.0.20
nitecrawler in ~ @ 19:18:31 $ ls -la /var/log/packages/gcc*
-rw-r--r-- 1 root root 31224 Aug 13 18:47 /var/log/packages/gcc-4.9.2-x86_64-3
-rw-r--r-- 1 root root 39080 Aug 13 18:47 /var/log/packages/gcc-g++-4.9.2-x86_64-3
-rw-r--r-- 1 root root 1936 Aug 13 18:47 /var/log/packages/gcc-gfortran-4.9.2-x86_64-3
-rw-r--r-- 1 root root 128184 Aug 13 18:48 /var/log/packages/gcc-gnat-4.9.2-x86_64-3
-rw-r--r-- 1 root root 10856 Aug 13 18:48 /var/log/packages/gcc-go-4.9.2-x86_64-3
-rw-r--r-- 1 root root 236242 Aug 13 18:48 /var/log/packages/gcc-java-4.9.2-x86_64-3
-rw-r--r-- 1 root root 2062 Aug 13 18:49 /var/log/packages/gcc-objc-4.9.2-x86_64-3
-rw-r--r-- 1 root root 771 Aug 6 01:49 /var/log/packages/gccmakedep-1.0.3-noarch-1
nitecrawler in ~ @ 19:18:58 $ ls -la /var/log/packages/glibc*
-rw-r--r-- 1 root root 353032 Aug 13 18:50 /var/log/packages/glibc-2.21-x86_64-2
-rw-r--r-- 1 root root 262917 Aug 13 18:50 /var/log/packages/glibc-i18n-2.21-x86_64-2
-rw-r--r-- 1 root root 1023 Aug 13 18:51 /var/log/packages/glibc-profile-2.21-x86_64-2
-rw-r--r-- 1 root root 8495 Aug 13 18:45 /var/log/packages/glibc-solibs-2.21-x86_64-2
-rw-r--r-- 1 root root 70109 Aug 13 18:51 /var/log/packages/glibc-zoneinfo-2015c-noarch-1
You appear to be at a slackware64-current level but be aware that at first, you had my multilib versions of gcc and glibc installed. Your most recent post shows that you now have the Slackware original packages installed for gcc and glibc which means your computer lost its ability to run (and compile) 32-bit programs.
Perhaps that was your intention. If you do not run any 32-bit software (Skype, Steam Client, Wine) then the situation is OK. Otherwise, check out what you need to do in order to get back that multilib capability: http://docs.slackware.com/slackware:multilib
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.