[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-15 13:47 -------
Subject: Re:  gcc_s not found when linking 64-bit C++

On Thu, 15 Jul 2004, ebotcazou at gcc dot gnu dot org wrote:
>>
>> since my objective is to create a directory tree for 100% 64-bit
>> development and I don't want to take the risk of failure while
>> upgrading the compiler.
>
> This will not change anything, --disable-multilib has nothing to do here.
>
> I'd suggest as a temporary workaround:
> - either to use --enable-version-specific-runtime-libs with a 32-bit multilib
> compiler, and to wrap up 'gcc -m64' in a shell script 'gcc64',
> - or to drop --enable-version-specific-runtime-libs with the 64-bit compiler,
> using a special --prefix instead.

I already have a 32-bit multilib compiler that works fine for building 
64-bit binaries.  However, my objective is to build a completely 
native 64-bit compiler using a special --prefix. This compiler should 
not requre that special -L flags be provided in order to achieve 
linkage to its own components.

The reason for this multi-day effort has been that I want 'make 
distcheck' to succeed when using 64-bit compilation.  Instead it ends 
up with a mis-mash of 32-bit and 64-bit files and fails.  I 
incorrectly assumed that requesting the 64-bit target would provide a 
64-bit build with libraries in the traditional locations.

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


-- 


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