Adding 2.18 symbols to 2.17 creates a hybrid whose macros still
present the release as 2.17. If I change the macros then it truly
is a 2.18 release.
I count at least 6 symbols versioned at GLIBC_2.18 that would need
to be added to support a compatible 2.18 ABI:
* __cxa_thread_atexit_impl
* __issignaling
* __issignalingf
* __issignalingl
* pthread_getattr_default_np
* pthread_setattr_default_np
This release behaves more like 2.17 than 2.18, but has a 2.18 ABI.
I know of no major distribution that has shipped a hybrid like this.
I don't know what other risks there might be with this solution...
... and that worries me.