During our work to establish a build baseline for 2.5.5, we have uncovered some facts that seem to undermine the value of the glibc version check that we perform.

Specifically, it is possible that when building on a system offering glibc > 2.2 the generated binary may only be dependent on GLIBC_2.2 level symbols, but still may not be able to run on systems offering only glibc 2.2.

The incompatibility arises when the system gcc has been configured to expect feature support compatible with a glibc newer than 2.2, since that is what is shipped on the system (see DT_GNU_HASH and https://bugzilla.redhat.com/show_bug.cgi?id=482848).

Since our glibc version check can't detect this sort of misconfiguration, it doesn't actually offer any protection, and we should remove it.