On (02/03/11 15:41), Phil Blundell wrote: > On Tue, 2011-03-01 at 11:47 +0000, Otavio Salvador wrote: > > On Tue, Mar 1, 2011 at 11:35, Phil Blundell <[email protected]> wrote: > > > On Mon, 2011-02-28 at 19:33 +0000, Otavio Salvador wrote: > > >> On Mon, Feb 28, 2011 at 17:17, Phil Blundell <[email protected]> wrote: > > > I just tried linking xfreerdp by hand with gold and the resulting binary > > > seemed to come out fine. So I think this is indeed a bug in GNU ld. > > > > Personally I think we need to trace it down (we as project) since it > > can lead to broken and difficult to trace behaviour. It took 3 days > > until I managed to identify the symbol failure. > > Yeah, that might be true. Or we could maybe just switch the default > linker to be gold, at least on targets that it supports.
Yes I have been doing this slowly for ARM. but probably it will be better with gcc 4.6 where linker will be selectable with options > > > I am far from an expert on linking and GNU ld. For debugging it I'd > > need guidance. > > I think the place to start looking would be _bfd_elf_merge_symbol(), > which is in bfd/elflink.c. This gets called by > elf_link_add_object_symbols() to record the syms that it finds and I > suspect that one or other of those functions is probably doing the wrong > thing. > > Or, if you don't want to debug it yourself, you could try to create a > testcase that shows the problem and then file a bug report with binutils > upstream. > > p. > > > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel -- -Khem _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
