This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: __register_frame_info & shared library compatibility
- To: Zack Weinberg <zack at rabi dot columbia dot edu>
- Subject: Re: __register_frame_info & shared library compatibility
- From: Jeffrey A Law <law at upchuck dot cygnus dot com>
- Date: Tue, 06 Apr 1999 17:46:23 -0600
- cc: Eric Kidd <eric dot kidd at pobox dot com>, otaylor at redhat dot com, egcs at egcs dot cygnus dot com
- Reply-To: law at cygnus dot com
In message <199904062115.RAA15222@blastula.phys.columbia.edu>you write:
> The best suggestion I can make is: Get glibc 2.1 and compile it with
> egcs. When you do that, glibc absorbs and re-exports the runtime
> functions that are causing the problem. Everything else will pick
> them up from there instead of libgcc.a. You'll have to recompile any
> libraries which are currently exporting __register_frame_info. You
> will not be able to run binaries built in this environment on
> non-glibc-2.1 systems.
>
> You can not do this with glibc 2.0 because then you lose binary
> compatibility with glibc 2.0 compiled by gcc 2.7 (exact same problem
> as you describe).
This points out the terrible problem with the patch to make the *_frame_info
functions weakly referenced in crtstuff.
We're already getting reports of programs that no longer run because of this
change. We may have to revert it.
jeff