We're delighted to announce the schedule, and registration, for the upcoming CentOS Dojo in Brussels, on February 1, 2019, the day before FOSDEM starts.
Details are here: https://wiki.centos.org/Events/Dojo/Brussels2019
The schedule is still marked "Tentative" since I have not received confirmation from all of the speakers yet, but we're almost there.
Registration is FREE, but we do ask that you register anyways, since it helps us with venue planning and catering.
See you in Brussels!
Hi.
New to this list. If this has been answered/resolved already, please point me to the solution.
In a very recent update to CentOS 7 libstdc++ has been altered in a way that has removed CXXABI_1.3.8 and GLIBCXX_3.4.20. I've noticed that this has broken a number of executables linked on other systems that used to run on CentOS 7. Is there any fix for this short of backing off the update?
Ubuntu seems to still allow these broken images to run. But I want the solid reliability CentOS has. If somebody can give me examples of Ubuntu up and running actual programs for a year plus then I'll gladly switch. I've never heard of Ubuntu dong that. I have had CentOS do that for me.
Thank you.
On Tue, Nov 13, 2018 at 12:10:22PM -0500, Chris Johnson wrote:
In a very recent update to CentOS 7 libstdc++ has been altered in a way that has removed CXXABI_1.3.8 and GLIBCXX_3.4.20. I've noticed that this has broken a number of executables linked on other systems that used to run on CentOS 7. Is there any fix for this short of backing off the update?
I don't see any evidence that the libstdc++ in CentOS 7 ever had version definitions for CXXABI_1.3.8 or GLIBCXX_3.4.20. Both seem to only go up to CXXABI_1.3.7 and GLIBCXX_3.4.19, at least with the libstdc++ package.
Perhaps you built your binaries on a system with newer version definitions?
On 11/13/2018 12:50 PM, Jonathan Billings wrote:
On Tue, Nov 13, 2018 at 12:10:22PM -0500, Chris Johnson wrote:
In a very recent update to CentOS 7 libstdc++ has been altered in a way that has removed CXXABI_1.3.8 and GLIBCXX_3.4.20. I've noticed that this has broken a number of executables linked on other systems that used to run on CentOS 7. Is there any fix for this short of backing off the update?
I don't see any evidence that the libstdc++ in CentOS 7 ever had version definitions for CXXABI_1.3.8 or GLIBCXX_3.4.20. Both seem to only go up to CXXABI_1.3.7 and GLIBCXX_3.4.19, at least with the libstdc++ package.
Perhaps you built your binaries on a system with newer version definitions?
I believe most of the images were originally built for Ubuntu.
On 11/13/18 11:50 AM, Chris Johnson wrote:
I believe most of the images were originally built for Ubuntu.
Sounds like that you are trying to run some binaries that were built for Ubuntu, and the Ubuntu version they used has a higher ABI version than those in CentOS 7.
If these were software (proprietary or FLOSS) that were designed for Ubuntu but not CentOS, you'd likely meet some other problems even when the ABIs match. Ubuntu and CentOS have many differences.
For simplicity I'd choose to stay with Ubuntu. Ubuntu also has Long Term Support (LTS) versions that are supported for five years:
https://www.ubuntu.com/about/release-cycle
-
Chris Johnson -
Jonathan Billings -
Rich Bowen -
Yan Li