Roland Baumann writes:
> this patch indeed fixes my problem. Thanks a lot.
You're welcome. Thanks for reporting the bug.
> Actually, I am wondering whether it makes sense to use "-s" and
> "-shared" together. What information stays in the shared object that I
> am still able to link it?
An EL
Hi Ian,
this patch indeed fixes my problem. Thanks a lot.
Actually, I am wondering whether it makes sense to use "-s" and
"-shared" together. What information stays in the shared object that I
am still able to link it?
Roland
Ian Lance Taylor wrote:
Roland Baumann writes:
I compile this
Roland Baumann writes:
>>>
>>> I compile this with:
>>>
g++-4.1.2 -c test_shared.cc -o test_shared.o
g++-4.1.2 -B -shared -s test_shared.o -o test_shared.so
>>
>> I'm not able to recreate this problem with either binutils 2.19 or
>> with the development version. Can you post the outpu
I compile this with:
g++-4.1.2 -c test_shared.cc -o test_shared.o
g++-4.1.2 -B -shared -s test_shared.o -o test_shared.so
I'm not able to recreate this problem with either binutils 2.19 or
with the development version. Can you post the output of your -shared
command line with the -v option?
Roland Baumann writes:
> I have a problem with gcc 4.1.2 and the gold linker (from binutils
> 2.19). We build shared objects with options "-s" and "-shared"
> together. This leads to assertions in the gold linker. In most cases I
> see
>
> .../gold/real-ld: internal error in get_output_view, at
>
Hi,
I have a problem with gcc 4.1.2 and the gold linker (from binutils
2.19). We build shared objects with options "-s" and "-shared" together.
This leads to assertions in the gold linker. In most cases I
see
.../gold/real-ld: internal error in get_output_view, at
...src/binutils-2.19/gold/ou
