Mark Martin wrote:
> On 10/14/07, *Brian D. Horn* <Brian.Horn at sun.com 
> <mailto:Brian.Horn at sun.com>> wrote:
>
>
>     I just observed this late Friday and kind of figured out what is wrong
>     today.  After I'm sure how
>     to work around this problem (and it is only one problem) I'll post
>     the fix.
>
>     Brian
>
>
> Thanks for taking a look.  Are you saying the x86 build (rev 94) 
> suffers from this issue as well?
Yes.  The thing is that we hadn't been rebuilding the linker since we 
had it working properly
for building the boot and kernel, since we were not up to application 
code.  When, recently,
we started building application code (libc.so.1 and such) I found that 
there was a bug in the
linker (ld).  I went to fix that bug and cam across this error.  It has 
to do with the -W0,globalstatic option, but
I need to investigate a bit more to find out when and how this problem 
game into being.

Brian
>
>
> Games are over, so I threw some more compute cycles at it.
>
> Comparing some of those duplicate symbols to the objects produced by 
> the native onnv-gate in another workspace build I see..
> $ elfdump -s sparc/pics/cap32.o  | grep captype
>        [4]  0x00000040 0x00000014  OBJT LOCL  D    0 .rodata        
> captype
> $ elfdump -s sparc/pics/cap64.o  | grep captype
>        [4]  0x00000040 0x00000014  OBJT LOCL  D    0 .rodata        
> captype
>
> vs.
>
> $ elfdump -s ppc/pics/cap32.o | grep captype
>       [20]  0x00000000 0x00000014  OBJT GLOB  D    0 .rodata  
> $XAZL5GeBV$1IcCKzNKcCTXpTuDgWLfiA.captype
> $ elfdump -s ppc/pics/cap64.o | grep captype
>       [20]  0x00000000 0x00000014  OBJT GLOB  D    0 .rodata  
> $XAZL5GeBV$1IcCKzNKcCTXpTuDgWLfiA.captype
>
> So on to figure out why the scope difference (which I hope explains 
> the name mangling)..
>
> Mark
>
> -- 
> ------------------------------------------------------
> Born to the false world, the wanderer,
> Storyteller, The Pied Piper
> On a quest for immortality
> Gathering a troop to find the fantasy
> -- Nightwish 


Reply via email to