This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 01/30/14 21:36, Carlos O'Donell wrote:
To say the least. I pondered something along these lines to address some issues in the past, it's unpleasant on so many levels. And it feels a lot like a repeat of the gcc-2.96 fiasco.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.
Jeff
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |