This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.0 and multilibbing
- To: Alexandre Oliva <aoliva at redhat dot com>
- Subject: Re: gcc 3.0 and multilibbing
- From: Tom Tromey <tromey at redhat dot com>
- Date: 02 Mar 2001 11:15:52 -0700
- Cc: gcc-bugs at gcc dot gnu dot org
- References: <871ysl2nno.fsf@creche.redhat.com> <ory9uo62bi.fsf@guarana.lsd.ic.unicamp.br>
- Reply-To: tromey at redhat dot com
>>>>> "Alexandre" == Alexandre Oliva <aoliva@redhat.com> writes:
>> Why are multilibbed libgcc.so's installed differently from all other
>> multilibs? That seems odd.
Alexandre> I think the reasons are to avoid using the same SONAME for
Alexandre> incompatible multilibs, and to need a single additional
Alexandre> directory in ld.so.conf.
I don't understand the second part of this. Won't this only work for
C programs? Suppose I build a PPC `nof' C++ program. Won't it simply
fail, since the nof libstdc++ will be in an unsearched directory?
Or will gcc magically add the -rpath in this case but no other?
Tom