Hi Dimitri, That can be avoided building the RPMs on older RHEL distributions using the Red Hat Developer Toolsets that Greg and others mentioned. These toolsets include newer compilers, which however link the binaries against the GLIBC present in the distribution they run on, thus maintaining the backwards compatibility. For example, devtoolset-4 brings GCC 5.2 to RHEL 6:
http://developers.redhat.com/products/developertoolset/get-started-rhel6-cpp/ Cheers, p. > On 29 Sep 2016, at 20:14, Dimitri Maziuk <dmaz...@bmrb.wisc.edu> wrote: > >> On 09/29/2016 10:16 AM, Greg Landrum wrote: >> >> My hope is that all of those people will be able to keep happily >> using a reasonably up-to-date version of the RDKit. > > Well, that's kinda the point: there are no RPMs that let you run > binaries linked to GLIBC_2.17 on GLIBC_2.5, nor compile c++-14 code with > c++-03 compilers. > > -- > Dimitri Maziuk > Programmer/sysadmin > BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu > > ------------------------------------------------------------------------------ > _______________________________________________ > Rdkit-discuss mailing list > Rdkit-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
------------------------------------------------------------------------------
_______________________________________________ Rdkit-discuss mailing list Rdkit-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
