Comment #32 on issue 15984 by [email protected]:  
/usr/local/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found
http://code.google.com/p/chromium/issues/detail?id=15984

@rklloyd: FYI, the "bleeding edge distro" you refer to is... Ubuntu Hardy  
LTS. It
might be bleeding edge by Centos 5.4 standards, but it's a stable distro  
for the rest
of the world. There's every intention to ship software that will work out  
of the box
for the majority of users. Your speculation of Google only supporting  
bleeding edge
releases is wrong.

On Linux, the landscape is complicated. You have multiple distros, all of  
which
release at different intervals with (slightly) different versions of  
software. When
the majority of the distros support something, in this case, libstdc++  
3.4.9, we
decide it's safe to use. The line has to be drawn somewhere, and it's  
unfortunate
Centos is on the wrong side of that line.

So let's talk about Centos. You also sound very offended that we're not  
supporting
the "very latest release of the world's most popular commercial Linux." In  
reality,
that means RHEL/Centos only has ~2% of the Linux marketshare. [1] The world  
doesn't
resolve around Centos, most of the distros out there have moved forward,  
and they're
supported: Ubuntu 8.04 LTS and up, Debian 5.0 (stable), Fedora 11+,  
OpenSUSE 11+. If
Centos is dragging its feet (by design), there's nothing we can do about  
that.

However, there might be hope. If someone actually got it to compile without  
the need
for GLIBCXX_3.4.9, and it's not a ugly hack, then maybe that person can  
submit a
patch to Chromium and fix this. You should ask this Chris fellow how he got  
it to
work. (and buy him a tasty beverage.)

[1] http://www.desktoplinux.com/news/NS8454912761.html (sorry I can't seem  
to find a
newer survey, but you get the idea.)


p.s. I'm writing to you from Google Chrome on a Slackware 12.0 machine.  
Slackware
12.0 was released in mid 2007. It's libstdc++ was too old, and half the GTK  
libraries
needed to run Google Chrome... too old. Fortunately it wasn't very hard to  
upgrade a
few critical packages to a new version from Slack 12.2. :-) You just gotta  
think
outside the box sometimes.

p.p.s. I'm just the messenger, don't shoot the messenger. Of course _I_  
want Chromium
to run on more Linux distros, (more Chromium users == good) but there are  
constraints
and sometimes we can't make everyone happy. If I truly didn't care, I  
would've just
ignored this bug all together.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

-- 
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs

Reply via email to