<SOLVED> Installing viber; not executing

Issues related to applications and software problems
odysseus
Posts: 64
Joined: 2014/09/14 16:55:22

Re: <SOLVED> Installing viber; not executing

Post by odysseus » 2018/07/17 21:20:48

lightman47 wrote:
2018/07/15 21:20:33
... and was supplying your mobile number mandatory (and not troubling to you)?
Yes, you have to supply your number but I don't have trouble with that.

odysseus
Posts: 64
Joined: 2014/09/14 16:55:22

Re: <SOLVED> Installing viber; not executing

Post by odysseus » 2018/12/11 06:52:35

odysseus wrote:
2018/07/17 21:17:47
TrevorH wrote:
2018/07/15 21:54:21
Not to mention that you probably just broke your system rather badly...
Things seem to still work.
I should have been more patient, since the very best solution would have been to only copy "the recent version of libstdc++" into "/usr/lib64" instead of just doing "make install". So you had a point...

odysseus
Posts: 64
Joined: 2014/09/14 16:55:22

Re: <SOLVED> Installing viber; not executing

Post by odysseus » 2018/12/15 05:43:09

odysseus wrote:
2018/12/11 06:52:35

I should have been more patient, since the very best solution would have been to only copy "the recent version of libstdc++" into "/usr/lib64" instead of just doing "make install". So you had a point...
Like this: Image

dvershinnin
Posts: 1
Joined: 2019/06/18 10:47:57

Re: Installing viber; not executing

Post by dvershinnin » 2019/06/18 11:04:53

TrevorH wrote:
2018/01/04 16:00:48
No, that's the wrong solution. What that actually tells you is that the app was built to require a newer glibc package than we ship but if you attempt to change that, you will break the rest of your system so do not even try.
The error:

Code: Select all

/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found
Is for requirement to have a newer C++ (not C) std library. The file

Code: Select all

/lib64/libstdc++.so.6
ships with libstdc++- package not glibc.

Either way. Can you be more specific how updating to newer glibc would break system? So that your answer can be more elaborate.

If I drop in newer libc.so.6 , it provides prior ABI endpoints, e.g. if you run

Code: Select all

strings /usr/lib/libc.so.6 | grep --perl-regexp "^GLIBC_"
you can see a lot of those ABI versions like:

GLIBC_2.10
GLIBC_2.11
GLIBC_2.12
GLIBC_2.13
GLIBC_2.14
GLIBC_2.15
GLIBC_2.16
GLIBC_2.17
...

So how it breaks system exactly if it is satisfied with older ABI requirements using the new library?

User avatar
TrevorH
Forum Moderator
Posts: 25816
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: <SOLVED> Installing viber; not executing

Post by TrevorH » 2019/06/18 15:44:16

OK, let's put it a different way. Doing that would be completely unsupported and if you get any problems in future at all then the first response will be "reinstall your system".

All packages in CentOS are built against the version of glibc that we ship. Changing it is unsupported and will almost certainly break your system. Do not do so.
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

Post Reply