Re: Versioning problem with __register_frame

[Jakub Jelinek <jakub at redhat dot com>]

On Wed, Jan 30, 2002 at 01:45:35PM +0100, Andreas Schwab wrote:
> "Martin Schwidefsky" <schwidefsky@de.ibm.com> writes:
> 
> |> Does this mean that we have to make them GLIBC_2.0 versioned symbols
> |> although the earliest symbol set for s390x is GLIBC_2.2 ?
> 
> This will be automatically handled.  Even many Versions files list symbols
> under the GLIBC_2.0 version the shared library will not contain versions
> prior to the earliest version as specified in shlib-versions.  See the
> generated file Versions.all in the build directory to see how it works.

Though in this case it will cause only problems.
GCC libgcc-glibc.ver uses:

%inherit GCC_3.0 GLIBC_2.0
GLIBC_2.0 {
...
  __register_frame_info
...
}

So, either gcc needs to be changed so that for selected targets it will use
different symbol for these symbols instead of GLIBC_2.0, or glibc needs to
export them as GLIBC_2.0 unconditionally.

	Jakub