This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A completely different approach to EH runtime
- To: zackw at Stanford dot EDU (Zack Weinberg)
- Subject: Re: A completely different approach to EH runtime
- From: Joern Rennecke <amylaar at cambridge dot redhat dot com>
- Date: Thu, 22 Feb 2001 06:59:48 +0000 (GMT)
- Cc: hjl at valinux dot com (H . J . Lu),amylaar at cambridge dot redhat dot com (Joern Rennecke),aoliva at redhat dot com (Alexandre Oliva), gcc at gcc dot gnu dot org
> If we add symbols to libgcc_s.so, they will have a different symbol
> version (GCC_3.1 or something). The dynamic linker will be faced with
>
> binary uses: GCC_3.0 GCC_3.1
> /lib/libgcc_s.so: GCC_3.0
> /path/to/other/lib/libgcc_s.so: GCC_3.0 GCC_3.1
>
> I don't know if it is intelligent enough, in this context, to link
> only the libgcc_s.so in /path/to/other/lib. However, it will pick one
Couldn't you make the binary use only GCC_3.1 ?
Would that make it unambigous what to link?