![]() So, someone could easily go to the old version back, if he/she experienced some drawback. Then (after building the new gcc which build the new libstdc++.so.6 which is found in /usr/lib64, i installed the whole gcc4.8.1) i linked the symbolic link :-)įirst you have to make a copy (for safety) of the old "/usr/lib/libstdc++.so.6" (or the one, pointed to by this link). Maybe there will be a problem in future, but then i can decide to go back to the old library. I do not say that everybody should install the newest libstdc++, but for me this was the solution, i can use the newest compiler and, on top of that, the actual applications, so if it works for me, why should i omit this? Ok, a good backup strategy is mandatory, but since all important (am unimportant) application, even yum, are working, this is the right solution for me. I am bored to work the way, the OS drects me to do, i have the opinion that the OS should me in my work and not that i should to support the OS. Maybe there is a drawback (therefore i mentioned that jre1.7 java is not running with that library), but i was able to switch this version of the jre back and all thing on my system are quite healthy, there was no obstacle, at least, i didn´t recognized one. CentOS was designed around such central components like the libstdc++.so.6. You are right, when you say that the GLIBXXX_3.1.15 is not designed for CentOS 6 but i think rather that no central component like such a library is designed for a special OS, the other way round makes sense. I wouldn´t say say that i have "bodged" anything, i´d rather would call it an improvement of outdated libraries or a system. But with the "alternatives" solution, there is an option for me to switch back, but until now everything is fine for me and i have (until now) not recognized any drawback. Maybe this is not a solution for everyone, it requires a lot of fiddling and adjustments, so someone could never be sure, that this is working for every system. Since the official distributed qt seems too old, i am now able to run the actual qt5.0.2 Don´t really know, what is the reason for this, i suppose, that java1.7 refers to the old libstdc++6.0, but i am not shure.Īfter that preparation i was able to run the previously "qt-linux-opensource-5.0.2-x86_n" command, which installed the new version. With the "alternatives" command, i switched to java1.6 and java (and the applications) was running again. I installed a new java from oracle, but that was not the solution. Where the "+" indicates the actual active packet, in my case the new gcc 4.8.1Īfter that, java and all java applications were broken. Shows the diverse applications, for example for the "alternatives -config gcc" it displays now:Įs gibt 3 Programme, welche 'gcc' zur Verfügung stellen. With the "alternatives" command on linux i was able to preserve the old executables, the Then i downloaded the libstdc++.so.13 and made a symbolic link: When i did "strings /usr/lib/libstdc++.so.6" it didn´t showed the right GLIBCXX_3.4.15.Īt the same time i downloaded and installed the gcc 4.8.1 (for experimenting with C++11). So, now i have a working solution for me.īut i did lightly more than only to update the libstdc++.so.6. To open qt creator is it correct process? (:32637): Gtk-CRITICAL **: gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) (Details - 1: Failed to get connection to session: Did not receive a reply. GConf Error: Failed to contact configuration server some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. Qt: Session management error: None of the authentication protocols specified are supported QGtkStyle was unable to detect the current GTK+ theme. Source0: /qtcreator/qtcreator-dev.The version of qt is qt-4.6.2-26.el6_4.i686Īfter completion of installation I opened the qt using aks]# qtconfig-qt4 License: GPL-3.0-only WITH Qt-GPL-exception-1.0 %global _python_bytecompile_errors_terminate_build 0 # is not a valid python file, only for the IDE # We need avoid oython byte compiler to not crash over template. Blob Blame History Raw #define prerelease beta1
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |