SCIENTIFIC-LINUX-USERS Archives

July 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Yasha Karant <[log in to unmask]>
Reply To:
Yasha Karant <[log in to unmask]>
Date:
Wed, 3 Jul 2013 01:04:13 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
On 07/02/2013 04:47 PM, Steven Haigh wrote:
> On 3/07/2013 9:33 AM, Tam Nguyen wrote:
>> On Tue, Jul 2, 2013 at 6:45 PM, Yasha Karant <[log in to unmask]
>>> <mailto:[log in to unmask]>> wrote:
>>>
>>>     Add/remove software shows:
>>>
>>>     google-chrome-stable-28.0.__1500.70-209565 (x86_64)
>>>
>>>     but installation results in a transaction error:
>>>
>>>     google-chrome-stable-28.0.__1500.70-209565.x86_64 requires
>>>     libstdc++.so.6(GLIBCXX_3.4.15)__(64bit)
>>>
>>>     and the dependency does not automatically resolve.  Is there a
>>>     workaround for this
>>>     issue?
>  >
>> Download Google rpm here: http://orion.lcg.ufrj.br/RPMS/myrpms/google/
>> then yum install the download rpm.
>
> Sorry - but I think its really bad practice to just refer people to
> random, unknown repositories for common software...
>
> In a nutshell, the version of libstdc++ seems to be rather old that
> Google are using. SL has:
>
> # yum whatprovides libstdc++.so.6
> libstdc++-4.4.7-3.el6.i686 : GNU Standard C++ Library
> Repo        : sl6x
> Matched from:
> Other       : libstdc++.so.6
>
> I'd recommend is using chromium if you don't rely on any Google-only
> features.
>
> There is a thread about this on the SL forums:
>      http://scientificlinuxforum.org/index.php?showtopic=1134
>

I thoroughly am confused about these responses.  Unless I am mistaken, 
the chrome RPM seems to be from a standard EL6 repository.  Moreover, 
the previous release of chrome through this same method did not produce 
this error, and installed and ran without obvious issues.  However, as 
updates typically both fix bugs and security holes, we routinely update 
to current production.  It is only the most current release of "real" 
chrome (not chromium) that shows this problem -- is there a repository 
with the necessary RPMs for a proper workaround?

If not, in what ways does chromium (presumably, a port from the current 
production chrome source) differ from chrome?  If the difference merely 
is a lack of google services by default, but no loss of browser security 
or functionality, the chromium may be a superior choice.

Yasha Karant

ATOM RSS1 RSS2