This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Ericsson question about glibc 2.19 compatibility and RHEL 6.5.
- From: Ryan Arnold <ryan dot arnold at linaro dot org>
- To: Francesco Leone <francesco dot leone at ericsson dot com>
- Cc: "libc-help at sourceware dot org" <libc-help at sourceware dot org>, "IMSOmegaTeam (TEI)" <PDLIMSOMEG at ex1 dot eemea dot ericsson dot se>
- Date: Fri, 14 Mar 2014 09:51:22 -0500
- Subject: Re: Ericsson question about glibc 2.19 compatibility and RHEL 6.5.
- Authentication-results: sourceware.org; auth=none
- References: <392D042D79D5564ABA570472F766312421FB9A76 at ESESSMB306 dot ericsson dot se> <53221029 dot 1020704 at redhat dot com> <392D042D79D5564ABA570472F766312421FB9E37 at ESESSMB306 dot ericsson dot se> <07EAD5DC1C1C7141BF12FF052B5F7AB3038E049A at ESESSMB207 dot ericsson dot se>
On Fri, Mar 14, 2014 at 3:51 AM, Francesco Leone
<francesco.leone@ericsson.com> wrote:
> Dear folks,
>
> In our product we are going to introduce RHEL 6.5 and the new version of
> GNU C Library, glibc 2.19.
>
> My questions are:
>
> 1) Is glibc 2.19 compatible with RHEL 6.5 distribution?
>
> 2) Is glibc 2.19 compatible with java 1.7?
>
>
> Looking forward an early reply
Francesco,
If your product is to run on a pristine RHEL 6.5, I believe that the
version of glibc you need to link against is glibc 2.12.
This means that if you're building a toolchain that is designed to run
binaries on RHEL 6.5, you need to make sure your toolchain sysroot
doesn't have a glibc version that exceeds the version on RHEL 6.5.
Otherwise; you'll get lots of runtime errors where the loader (dynamic
linker) can't find the proper versioned symbols because the system
glibc is older than what was linked against (for instance if your
sysroot had GLIBC 2.19).
I don't know about Java compatibility with glibc 2.19.
--
Ryan S. Arnold
Linaro Toolchain Working Group
www.linaro.org