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.
For most slackbuilds the order is vital as the script won't build the package if dependencies aren't met usually (assuming no hand-tuning). For the google-chrome slackbuild it won't matter I don't think since the script is just repackaging a .deb binary package to a slackware friendly format and then installing it. If I remember right I missed the seamonkey dependency on my multilib system and installed it post chrome. On the other hand since you have a google-chrome package unless you deleted it, probably sitting in /tmp somewhere you can just removepkg google-chrome and then reinstall it after the seamonkey dependency.
Well, i am using slackware 13 but felt current would be the source closest to my platform. I certainly did not see were slackware 13 seamonkey can be sourced.
Actually I would prefer to install the minimal seamonkey-solibs ?
Well, i am using slackware 13 but felt current would be the source closest to my platform. I certainly did not see were slackware 13 seamonkey can be sourced.
Actually I would prefer to install the minimal seamonkey-solibs ?
OK I managed to install the seamonkey solibs but running into problems installing GConf.
Code:
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for glib-genmarshal... /usr/bin/glib-genmarshal
FYI: Will build without *any* debugging code
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether to build gtk-doc documentation... no
checking for gtkdoc-check... /usr/bin/gtkdoc-check
checking for DEPENDENT... configure: error: Package requirements (glib-2.0 > 2.14.0 gmodule-2.0 >= 2.7.0 gobject-2.0 >= 2.7.0 ORBit-2.0 >= 2.4.0 dbus-1 >= 1.0.0 dbus-glib-1 >= 0.74) were not met:
No package 'ORBit-2.0' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables DEPENDENT_CFLAGS
and DEPENDENT_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
I only need ORBit-2.0, right? Can that be found on slackbuilds?
Hello all, just updating you on google chrome installation. I started from scratch by rebuilding slackware. I then successfully installed orbit requiring no other dependencies followed by 64 bit seamonkey solibs. Then chrome itself. Followed by all the other desired packages.
updated the system. Unfortunately exactly as before google would not launch. It now requires
Code:
root@redeemer:/home/siawacsh# google-chrome
/usr/bin/google-chrome: error while loading shared libraries: libnssutil3.so.1d: cannot open shared object file: No such file or directory
root@redeemer:/home/siawacsh# google-chrome
/usr/bin/google-chrome: error while loading shared libraries: libnssutil3.so.1d: cannot open shared object file: No such file or directory
I am thinking why are these dependencies not listed clearly on the slackbuild site. I might have to rebuild google again...
root@redeemer:/home/siawacsh# google-chrome
/usr/bin/google-chrome: error while loading shared libraries: libnssutil3.so.1d: cannot open shared object file: No such file or directory
I am thinking why are these dependencies not listed clearly on the slackbuild site. I might have to rebuild google again...
If you do not install Slackware in full, then it will be your own responsibility to fill the gaps where they appear. Dependency information on slackbuilds.org will never contain packages that are already in Slackware.
The missing file "libnssutil3.so" is part of the "seamonkey-solibs" package. Which is part of Slackware itself, you'll find it in the "l/" directory.
If you do not install Slackware in full, then it will be your own responsibility to fill the gaps where they appear. Dependency information on slackbuilds.org will never contain packages that are already in Slackware.
The missing file "libnssutil3.so" is part of the "seamonkey-solibs" package. Which is part of Slackware itself, you'll find it in the "l/" directory.
Eric
Hi Allien_Bob, would care to be a bit more clearer. When I was rebuilding Slackware I took care to go for the default option of installing everything.
So, you saying is on the installation CD...???
If so, would please give me the command which would install that from the cd?
I certainly don't see a "l/ " directory. Perhaps you meant to / (root) but I used the whereis command to search for it without any results. Am correct in thinking that chrome has to be removed before this procedure?
Thanks in advance.
Look to see what libnssutil3.so.1d is linked to. Chrome uses several links to seamonkey by default. Firefox has the same files so you can relink these, or if you don't want Seamonkey at all you can probably get by with creating a symlink to point everything to firefox. This has worked for me when there were missing seamonkey packages.
I must note here, that when I installed 32 bit google-chrome on my multilib-current system recently I had to install an entire 32 bit seamonkey to get working SSL in google-chrome.
Look to see what libnssutil3.so.1d is linked to. Chrome uses several links to seamonkey by default. Firefox has the same files so you can relink these, or if you don't want Seamonkey at all you can probably get by with creating a symlink to point everything to firefox. This has worked for me when there were missing seamonkey packages.
I must note here, that when I installed 32 bit google-chrome on my multilib-current system recently I had to install an entire 32 bit seamonkey to get working SSL in google-chrome.
It does not look to be linked to anything. I am assuming >> indicates a link.
In any case I have flash working on firefox after the slackware rebuild. This brings me back to the issue of stability. I cannot getaway from idea that when we talk about slackware stability it must only relate to the base system. I.e. you don't watch movies online, don't require the latest office apps...etc
I have 4 slack systems and all of them work just fine to watch DVD's, youtube, hulu.com. My only complaint comes from flash's 64 bit support which lags WAY behind on 32 bit in my experience. With multilib I have no problems. As far as installing flash player I don't bother with a slackbuild since it's a single file being extracted and copied to the appropriate location.
If you didn't install the seamonkey solibs again then you didn't have nssutil3.so. It wasn't included in slack13 by default, and thus is in the "patches" directory from a slackware download mirror.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.