Libstdc ++. so.6: cannot open shared object file: no such file or directory

Source: Internet
Author: User

When installing cmake ,. /Bootstrap does not work at this step. It is said that the C ++ compiler is lacking. After opening the specified log, the root cause is libstdc ++. so.6 cannot find the problem. I searched many methods on the Internet. The reasons for the problem are as follows:

1. Without libstc ++. so.6 under/usr/lib, install the software package and create a soft link.

2. conflicts occur between/usr/lib and/usr/local/lib or libstc ++. so.6 of/usr/lib64,

See the analysis http://blog.csdn.net/jindingwang/article/details/7569466 for this log

The solution is written in the previous log.

Take the version inconsistency in/usr/lib64 as an example (in my case ),

In/usr/lib, libstdc ++. so.6 points to version 6.0.3. However, in/usr/lib64, a version pointing to libstdc ++. so.6 is 6.0.8. Therefore, copy version 6.0.3 to/usr/lib64 (in fact, there is 6.0.3 under my lib64, so I didn't copy it again) and re-establish the symbolic link.

However, after this step, the C ++ compiler issue is not reported by/Bootstrap, but the following error is reported:

/Usr/lib64/libstdc ++. so.6: Version 'glibcxx _ 3.4.5 'not found

It is found that the libstdc ++. so.6.0.* version is too low. It seems that the 6.0.3 link is not working, so I copied the 6.0.8 version under/usr/lib64

In/usr/lib, reconnect and find that libstdc ++. so.6 is not found .... Later, I downloaded version 6.0.13 and copied it to the two directories to create soft links in their respective directories. Still cannot find libstdc ++. so.6. Then, the test points the soft connection under lib64 to 6.0.13 under Lib, which still fails. Establishing a soft connection in the opposite direction still reports the previous error. Sad reminder ....

 

Later, run the locate command to find a 6.0.9 package under/usr/local/lib64, and copy the package to/usr/local/lib and/usr/lib, under/usr/lib64, establish soft connections under their respective directories. The final command runs successfully.

 

I guess it is because I deleted both. so.6 and 6. 0. * under/usr/local/lib? This is not the reason... Or is the version 6.0.9 that is linked to the. so.6 file in/usr/local/lib64 in conflict with the version 13? But why not conflict with version 6.0.3 when the first uniform version is 6.0.3?

 

 

 

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.