I'm developing an python application for my company on a RHEL 7.4, development environment. In my prod env, I'm running a RHEL 6.8 (soon to be upgraded). The problem is that I ran my application on testing env without problems, but on prod I'm facing various problems due to package versions. I've upgraded most of them, but now I have to install glibc-2.14. I've downloaded the package from the oficial repository, created a new build, ran make and waited several minutes for it to finish. My question is: is there any problem on installing that glibc on prod? I mean, could that "break" the OS on some way?

1 Answer 1


Yes, upgrading the C library is a risky endeavour and could break the system, possibly in non-obvious ways. Upgrading the GNU C library within Red Hat Enterprise Linux goes into details. You might run into issues with support too.

If the RHEL 6 system is soon to be upgraded to RHEL 7, your best bet might be to wait for that. As Philip Couling says, if your development and production environments don’t match, you’re testing in production anyway. Alternatively, you could look at the Developer Toolset which will allow you to build and run compatible programs for RHEL 6 and 7, with newer versions of GCC and the C library.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .