Re: Symbol redefinition bugs

[Jeff Bailey <jbailey at raspberryginger dot com>]

On lun, 2005-11-21 at 13:01 -0800, Roland McGrath wrote:
> > Done this way, readelf -a showed that the various symbols went from being
> > WEAK to being GLOBAL.
> 
> Which symbols?  Show the exact details you are talking about.

This is on powerpc-linux using readelf -a.
The "old" build, is CVS HEAD glibc as of 2005-11-17 using binutils
2.16.1.  The "new" build is CVS HEAD glibc from today, using binutils
CVS from 20051117.

old:
   617: 000d85ac    44 FUNC    WEAK   DEFAULT   10 socket@@GLIBC_2.0
   954: 000d807c    44 FUNC    WEAK   DEFAULT   10 bind@@GLIBC_2.0
  1014: 000d8550    52 FUNC    WEAK   DEFAULT   10 setsockopt@@GLIBC_2.0
  1253: 000d81c0    40 FUNC    WEAK   DEFAULT   10 listen@@GLIBC_2.0
  2184: 000d8160    44 FUNC    WEAK   DEFAULT   10
getsockname@@GLIBC_2.0

new:
   617: 000d861c    44 FUNC    WEAK   DEFAULT   10 socket@@GLIBC_2.0
   954: 000d80ec    44 FUNC    GLOBAL DEFAULT   10 bind@@GLIBC_2.0
  1014: 000d85c0    52 FUNC    GLOBAL DEFAULT   10 setsockopt@@GLIBC_2.0
  1253: 000d8230    40 FUNC    GLOBAL DEFAULT   10 listen@@GLIBC_2.0
  2184: 000d81d0    44 FUNC    GLOBAL DEFAULT   10
getsockname@@GLIBC_2.0

With the patch I offered, it keeps these symbols as weak on ppc.  I had
tested it against ppc and x86_64.

x86_64 also had these symbols as weak before, but i386 did not:

   944: 000b90f0    57 FUNC    GLOBAL DEFAULT   11 bind@@GLIBC_2.0
(etc)

If you want bind, setsockopt, listen, and getsockname as weak, I'll redo
the patch against current CVS and resubmit.

Tks,
Jeff Bailey