Re: Incremental linking

[hjl@lucon.org (H.J. Lu)]

> However, the desired use for this relinkable file is to be able to say
> something like:
> 
> gcc relinkable.o module1.o module2.o ... -o my_proggy
> 
> Where module1.o and module2.o may already be in the relinkable.o file, but
> because they've been specified on the command line, the symbols in those
> module*.o files override the symbols in the relinkable.o file.  Is there a
> way to get ld to behave this way?  Or was that half of the incremental

I am not sure. I think it is a linker bug.

> 
> We've also tried creating shared libraries which I guess basically defers
> the link until each module is needed at execution time.  This speeds
> things up rather a lot, but we noticed that gdb doesn't debug shared
> libraries very well for us.  If you step into a function that's in a

That is another linker bug.

> shared library, instead of popping in, it gets confused about what line
> number you're on, or it'll start stepping through what looks like
> hash-table glue code.  Not being able to debug hurts.

Please get binutils 2.8.1.0.30 from

ftp://ftp.yggdrasil.com/private/hjl

It should solve your shared library debugging problem. Let me know
if it doesn't work for you.


H.J.