[Bug 1572569] Re: Relocation error in libc.so.6

2017-10-17 Thread Adam Conrad
It's a "serious" suggestion in as such as no software that you want to run on multiple libc versions should EVER use private symbols. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572569 Title: Rel

[Bug 1572569] Re: Relocation error in libc.so.6

2017-02-12 Thread Vadim Peretokin
Is that a serious suggestion though? Because in order to get your software deployed on older versions of Ubuntu, you must compile on the older version of the OS, not on a newer one. This is catch-22 advice right here. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1572569] Re: Relocation error in libc.so.6

2016-05-01 Thread Adam Conrad
The private symbol __get_cpu_features@@GLIBC_PRIVATE has moved from libc6 to ld-linux-x86-64.so.2 where it belongs. ABI stability for private symbols is not guaranteed and, frankly, I'm not sure why you'd be linking to it at all. Without more info about how you managed to create this situation, m