This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Sat, Nov 24, 2001 at 05:13:03PM -0600, Berk, Murat wrote: > I reduced it to a small script but I had to include our .o files and 2 > libraries which trigger this. Thanks for your testcase. I am able to create a small testcase based on yours. The current Linux linker, 2.11.92.0.10, will detect the loop: # make cc -g -O -fPIC -c -o foo1.o foo1.c cc -shared -o libfoo1.so foo1.o -Wl,--version-script,libfoo1.map cc -g -O -fPIC -c -o foo2.o foo2.c cc -shared -o libfoo2.so foo2.o -Wl,--version-script,libfoo2.map cc -g -O -fPIC -c -o bar.o bar.c cc -nostartfiles -nostdlib -shared -o libbar.so bar.o libfoo1.so libfoo2.so /usr/bin/ld: libfoo2.so: indirect symbol `foo' to `foo@@ver1' is a loop libfoo2.so: could not read symbols: Invalid operation collect2: ld returned 1 exit status But on the other hand, I think it is a linker bug. I am looking into it now. H.J.
Attachment:
bug.tar.gz
Description: GNU Zip compressed data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |