This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/16507] gcc_s not found when linking 64-bit C++
- From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Jul 2004 14:38:29 -0000
- Subject: [Bug c++/16507] gcc_s not found when linking 64-bit C++
- References: <20040713003639.16507.bfriesen@simple.dallas.tx.us>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-07-13 14:38 -------
> 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?
That's the whole question. The default directory $(prefix)/lib is 32-bit on
Solaris, $(prefix)/lib/sparcv9 being the 64-bit directory, both for the
sparc-sun-solaris2.* and the sparc64-sun-solaris2.* compilers. Now
$(prefix)/lib/gcc/$(target)/$(gcc-version) is 32-bit with the
sparc-sun-solaris2.* compiler and 64-bit with the sparc64-sun-solaris2.*
compiler. So all of this becomes very messy when
--enable-version-specific-runtime-libs comes into play in the latter case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16507