This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [3.2] HELP! How can I move libgcc_s symbols from version GLIBC_2.0 to GCC_3.0 keeping backwards compatibility?
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 2 Aug 2002 00:34:34 +0200
- Subject: Re: [3.2] HELP! How can I move libgcc_s symbols from version GLIBC_2.0 to GCC_3.0 keeping backwards compatibility?
- References: <200208020027.15288@enzo.bigblue.local>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Aug 02, 2002 at 12:27:15AM +0200, Franz Sirl wrote:
> Hi,
>
> I'm lost in symbol versioning. Currently due to a mistake on powerpc-linux-gnu
> the 4 symbols __[u]divdi3 and __[u]moddi3 are versioned as GLIBC_2.0 instead
> of GCC_3.0. I tried to fix it with an corrected libgcc-glibc.ver version
> script and a small assembler source.
> I able to get both __divdi3@GCC_3.0 and __divdi3@GLIBC_2.0, but I want GCC_3.0
> as a default version __divdi3@@GCC_3.0. How can I accomplish that?
See what e.g. s390 does. You certainly don't
need any small assembler source, just cannot use the "generic" linux
libgcc-glibc.ver, which means using something like:
SHLIB_MAPFILES = $(srcdir)/libgcc-std.ver $(srcdir)/config/rs6000/libgcc-glibc.ver
in your config/rs6000/t-linux*.
Jakub