![]() The yum packet manager seems to function in a normal way and if there should be a problem, i would try to fix this as well, but there is no problem (until now). while i am working without flaws with this solution. Maybe this has a drawback, but someone should explain where the drawback is when using a newer libstdc.so.6. I know, i know, every fundamental CentOs prayer would like to lapidate me for that, but i am bored in using old software only for idealistic reasons of others. (I don´t know if i am willing to invest more time in java.) Only java was complaining about the libstdc++.so.6, but since java (jre-1.7.0) is not in my main focus i switched java back to jre-1.6.0. I secured this with the "alternatives" command, but i am quite certain that this is not mandatory. To ensure that all depending applications would find "their" libstdc++.so.6. ![]() gcc 4.8.1 comes with the gcc 4.8.1 sources and the actual libstdc++.so.6. I have updated the antiquated libstdc++.so6 because i was nerved that is was impossible to install actual software, every time the linker was complaining about that it didn´t find the GLIBCXX_3.4.15.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |