[Bug c++/16507] gcc_s not found when linking 64-bit C++

["bfriesen at simple dot dallas dot tx dot us" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From bfriesen at simple dot dallas dot tx dot us  2004-07-13 14:15 -------
Subject: Re:  gcc_s not found when linking 64-bit C++

On Tue, 13 Jul 2004, ebotcazou at gcc dot gnu dot org wrote:

>
> ------- Additional Comments From ebotcazou at gcc dot gnu dot org  2004-07-13 13:51 -------
>> Right.  I used a wrong command in my bug report, however, the actual
>> condition remains.  Here is the good stuff:
>>
>> blade:gcc/sparc64-sun-solaris2.9/3.4.1# pwd
>> /usr/local/sparc64/lib/gcc/sparc64-sun-solaris2.9/3.4.1
>> blade:gcc/sparc64-sun-solaris2.9/3.4.1# file libgcc_s.so.1
>> libgcc_s.so.1:  ELF 32-bit MSB dynamic lib SPARC32PLUS Version 1, V8+
>> Required, dynamically linked, not stripped
>
> Okay. I'm a bit surprised by the error message issued by the linker though.

It does not surprise me since the linker never found a 64-bit 
libgcc_s.so in the search path. The Sun linker simply ignores 32-bit 
libraries..  If the linker had been requested to use a specific 
library file, and it was the wrong type, then the error would have 
been different.

>> So there is either a problem with the specs file, or the default
>> libgcc_s.so is expected to be 64-bit (but is not).
>
> It's a bad interaction between --enable-version-specific-runtime-libs and the
> multi-os-directory feature.

That's what it looks like to me.  There are a lot of variables here.

Should the default libgcc_s.so.1 be 64-bit for this target or should 
the specs file always look in the sparcv9 subdirectory by default?  I 
can manually fix the compiler install but I would like to do it 
correctly.

Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16507