4 ms·

Because the personal machine might be used to develop for a production machine running RHEL 6, and that cannot be upgraded because reasons(no time, software doe

Because the personal machine might be used to develop for a production machine running RHEL 6, and that cannot be upgraded because reasons(no time, software doesn't support RHEL 7 yet, $precious_driver doesn't support RHEL 7, + a lot of other reasons that makes sense to an OPS person but not a developer). Binaries created on RHEL 7 does not run on RHEL 6 - even when linking statically appears to work, you run the risk of running into the unforseen. You could develop on RHEL 7 and build for production on RHEL 6, but this causes you enough grief and trobleshooting nesting up in all kinds of minor differences to not make it worth it. Best you can do if you cannot upgrade from RHEL 6 is to install devtoolset(https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/ https://www.softwarecollections.org/en/scls/rhscl/devtoolset... - these are official packages crerated by Red Hat) to get a newer compiler.

thawkins 9y ago
Load fedora 27, and put all your legacy projects into a rhel6 docker container, with your workspace volume mapped into a "projects" folder, that way you also get to play your code with multiple rhel variants.
gnufx 9y ago
The only major difficulty in my experience doing EPEL/Fedora builds from the same source has normally been the prohibition on using SCLs in EPEL, which at least has been relaxed recently to allow devtoolset on EPEL. You can build for EPEL6 just fine on RHEL7, assuming you have the privilege to run mock. (EPEL packages are currently built on Fedora 27.)