This library needs to be used by a client s/w which accepts only the shared library. As another alternative, I had compiled all the dependencies of this library with fPIC on gcc 4.8 and linked them statically, except system libraries like libc, libstdc++,libpthread etc. Is it advisable to to compile libc, libstdc++ etc also with fPIC and link them statically. On Thu, Jun 23, 2016 at 4:35 PM, Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx> wrote: > On Thu, Jun 23, 2016 at 12:59 PM, Dinesh Pathak <dinesh.pathak@xxxxxxxxx> wrote: >> Hi, I have written a shared library using C++11 features, compiled >> with gcc 4.8, libc 2.18, which needs to be run on a client's CentOS 6 >> machine, which has gcc 4.4.7, libc 2.12. There are some symbols in >> this library which are not found in libc 2.12, so how can I use this >> library on CentOS 6. I have flexibility in how, where, which machine >> the library can be compiled, but eventually it should be usable on >> client CentOS 6, where packages can not be touched. >> If I compile the library using DevTools-2 on CentOS 6, can there can >> be any ABI related issues between these two versions of gcc/g++. >> Please let me know if there are any other suggestions.Thanks in advance. > > You did not explain why you need a 'shared' C++11 library (eg. why not > static in which case the problem would be mostly done). > > > -- > Mathieu
