It had been 3 months since I last updated Google Chrome on my main Slack64 13.37 multilib workstation, so I thought it was about time. I manually ran my custom version of Ruario's awesome script to retrieve, package and update my system with the latest version of Chrome, which is 29.0.1547.65. To my surprise, the updated application failed to run, with the system complaining that it needed GLIBCXX_3.4.15 from libstdc++.so.6 in order to start the binary.

After reverting to my previous version (27.0.1453.110), I began searching for answers. It didn't take long to find that Google ruffled quite a few feathers (particularly in the RHEL6/Centos/etc. crowd) by initially informing them that they were running an obsolete operating system and that Google would no longer support it. (We won't discuss their support of MUCH older closed-source proprietary operating systems made by other prominent vendors) They later softened the language of their notification, but the end result is still the same.

How convenient.

Before I invest a lot of time in a solving this (such as compiling my own multilib gcc/glibc, or upgrading Slack64, or finding and installing the needed libs in a custom location specifically for Chrome, or -- ?), I wonder if anyone else has already dealt with this issue and come up with a tidy solution?

@Col-Panic: If the binaries they provide need a newer Glibc I don't think there is much you can do about it. Either try compiling Chromium from source and see if that works, upgrade to Slackware 14.0 (I'm running it and can use the latest versions of Chrome) or find another browser.

P.S. I'm at least glad the script has been useful to you.

You could try a chroot of Slackware 14.0 (or -current) and run Chrome from there. Somewhat of an overkill but perhaps you will consider it better than upgrading Slack. I wouldn't but not everyone is me.

Absolutely, thanks!

Well, maybe I should just sit tight and wait until 14.1 and do a complete upgrade rather than implementing a hack.