Hi,
I am running Slackware 13.37 and have just installed the latest google chrome browser with the build script in /extra. I have also installed GConf, ORbit2, google-chrome-pam-solibs also located in /extra. However, when I start google-chrome I get the following error:

/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /usr/bin/google-chrome-stable)

What am I missing ?

Hey Dauer,

First thing I'd ask is are you going to upgrade? If so, I wouldn't follow any of these steps, I'd just updgrade.
1: Check and see that you downloaded from 13.37/extra and not 14./extra/ or current/extra. They roll the glibc forward with (almost) every revision.
2: If it says it can't find something that normally means it's not there. /usr/lib is in your $PATH, you can check by typing $PATH on the command line but if it's not, you've got bigger problems than chromium (don't worry, it is).
3: Check to see what's on the box, do a slocate for the glibc revision it's asking for, if you don't know how to set up slocate, post back and I'll give you a hand. If you don't find it with the exact revision, start chipping off the trailing numbers and replacing them with expansion characters. When you get a result, post it.

Chrome is distributed as binaries. The binaries are compiled on a distro which has a glibc that's too new for Slackware 13.37.
Here are the relevant strings in the glibc library of Slackware 13.37:
You see that 3.4.15 is not listed.
It means that you have to upgrade your Slackware to 14.0 or better: 14.1. An upgrade of just glibc is out of the question unless you know very well what you are doing.

Eric

1 members found this post helpful.

Thanks, that will come in handy

Thank you both for the help. I should probably consider an upgrade, but when you have a running version of Slackware where things are set up the way you want it you don't really fell the need to upgrade.

Until now.
You'll notice with increasing frequency that software will no longer work with your distro, once that distro starts aging.
I run servers on Slackware 13.37 still, and that gives me headaches from time to time when I have to use new software.

Eric

Hey Dauer,

If you run slackpkg every week, you don't really notice the revisions. A lot of people don't like slackpkg because you can't play with the ./configure switches if the packages auto-install, but if you set it to "download only" you can do whatever you like with them prior to installation, just don't let them pile up on the workbench, to the point you're installing dozens of them in a single day.
That's the only time I've ever run into trouble.

I've found, if you want to do this, it works best if before you start tinkering, sort the download directory by date of modification ( ls -lt) and install oldest to newest, that's the way slackpkg was planning to install them. If you touch one before you capture that data, they will get out of order so do it first thing.
As far as version changes, I find that as long as I can get back into the file system in the old install, I can pull whatever I need into the current system to make it feel familiar and comfortable. I just split my drives and mount the old partition anywhere my $PATH variable is not going to see it. So by the time I'm installing over Slackware 12 it's with Slackware 14 and I've been using Slackware 13 so long I've pretty much forgotten 12.
Just some thoughts, enjoy your weekend.

Why don't you try out Chromium? If you build it yourself from source, the GLIBC version shouldn't really matter.

Actually, that will be quite an adventure if you try it on Slackware 13.37.
When this thread was created two days ago, I decided to give building chromium a new try.
Just an hour ago, after about 10 re-tries, I finally ended up with a working chromium browser.
However I had to modify my chromium.SlackBuild quite a bit in order to use less of the system libraries (many of which are just too old in Slackware 13.37), I had to disable Native Client support because I could not fix the compilation errors caused by Google's binary pNaCl SDK; I needed to write a patch to eliminate compilation failures because of the missing multitouch support in the X.Org of Slackware 13.37, and I had to compile a Python 2.7 package (Slackware 13.37 still has Python 2.6).

If anyone is interested, I will upload the packages (in which case I will build a 32-bit version too. I only build for 64-bit because that is what my servers are running).

Eric

1 members found this post helpful.

I'd say yeah, just out of curiosity about how you hacked the install script to make that happen but as far as I'm concerned, I wouldn't have a use for it.
From what I'm seeing, I'd be more interested in improving virtual support for the distro. That's why I can't get my people to sign off on Slackware on the workstation, I spend 10 hours a day marooned in RHELtopia. It's full of windows users with RHEL certs... hell basically.
Edit: Can you point me to a thread or group that's working on this? I'd really like to try to help.