4 ms·

The GCC in CentOS 7 (what we use at work for being 'stable') doesn't even support C++14. In 2022.

by Shorel 4y ago

ncmncm 4y ago
This is meaningful, how? You are using a snapshot frozen years ago. Surprise, frozen thing is still frozen! You are of course able to build for frozen system with modern compilers (e.g. "dev-toolset-11". If you don't, it is because, and only because, your employer has chosen not to. My recommendation is, get a better employer.
- Shorel 4y ago
  I complained, and now I have an Amazon Linux 2 machine to play. Why the default is that horrible CentOS (I am an Ubuntu person), is beyond me. It's been decades since Oracle stopped being relevant (only reason to ever pick up a RedHat compatible distro, IMO).
  - ncmncm 4y ago
    CentOS 8 was released (and itself frozen, except security patches) years ago. Current CentOS has been broken loose from RHEL, so if you need bitwise compatibility with RHEL 9, you will need to switch over to building for Rocky or Alma when you move off targeting 7 or 8. You can build for CentOS 7 in a docker image on your Amazon host, and also run Gdb on your Amazon host, using "target remote" to attach it to a gdbserver on your CentOS 7 target execution environment. I use sshfs on my host to map a directory on the target, so my builds put binaries over there automatically.
    - Shorel 4y ago
      The issue is: I am testing graviton instances, because they are supposedly cheaper than Intel/AMD ones. Some 'normal' libraries still don't exist for ARM, and I have to compile more stuff myself. My own C++ code is the one requiring GCC 5 or higher.
      - ncmncm 4y ago
        Again, there is no difficulty of any kind in using (say) Gcc-11 to build binaries to run on a stock CentOS 7 target. On CentOS (which user-space environment you would run in a docker image), I think the package you would need is dev-toolset-11. Look it up. (It is possible that is only in CentOS 8, so you might need dev-toolset-9 instead, which would serve.)

The GCC in CentOS 7 (what we use at work for being 'stable') doesn't even support C++14. In 2022.

by Shorel 4y ago

The GCC in CentOS 7 (what we use at work for being 'stable') doesn't even support C++14. In 2022.

This is meaningful, how? You are using a snapshot frozen years ago. Surprise, frozen thing is still frozen! You are of course able to build for frozen system with modern compilers (e.g. "dev-toolset-11". If you don't, it is because, and only because, your employer has chosen not to. My recommendation is, get a better employer.

Shorel 4y ago
I complained, and now I have an Amazon Linux 2 machine to play. Why the default is that horrible CentOS (I am an Ubuntu person), is beyond me. It's been decades since Oracle stopped being relevant (only reason to ever pick up a RedHat compatible distro, IMO).
- ncmncm 4y ago
  CentOS 8 was released (and itself frozen, except security patches) years ago. Current CentOS has been broken loose from RHEL, so if you need bitwise compatibility with RHEL 9, you will need to switch over to building for Rocky or Alma when you move off targeting 7 or 8. You can build for CentOS 7 in a docker image on your Amazon host, and also run Gdb on your Amazon host, using "target remote" to attach it to a gdbserver on your CentOS 7 target execution environment. I use sshfs on my host to map a directory on the target, so my builds put binaries over there automatically.
  - Shorel 4y ago
    The issue is: I am testing graviton instances, because they are supposedly cheaper than Intel/AMD ones. Some 'normal' libraries still don't exist for ARM, and I have to compile more stuff myself. My own C++ code is the one requiring GCC 5 or higher.
    - ncmncm 4y ago
      Again, there is no difficulty of any kind in using (say) Gcc-11 to build binaries to run on a stock CentOS 7 target. On CentOS (which user-space environment you would run in a docker image), I think the package you would need is dev-toolset-11. Look it up. (It is possible that is only in CentOS 8, so you might need dev-toolset-9 instead, which would serve.)