This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [3.4/3.5 PATCH/RFA] Fix SH bootstrap failure (PR 15120)
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>
- Cc: gcc-patches at gcc dot gnu dot org, Mark Mitchell <mark at codesourcery dot com>, joern dot rennecke at superh dot com
- Date: 13 May 2004 04:38:32 -0300
- Subject: Re: [3.4/3.5 PATCH/RFA] Fix SH bootstrap failure (PR 15120)
- Organization: Red Hat Global Engineering Services Compiler Team
- References: <20040425.092155.98879005.kkojima@rr.iij4u.or.jp>
On Apr 24, 2004, Kaz Kojima <kkojima@rr.iij4u.or.jp> wrote:
> - alpha* | mips* | hppa* | i*86 | powerpc* | sparc* | ia64* )
> + alpha* | mips* | hppa* | i*86 | powerpc* | sparc* | ia64* | sh* )
> lt_cv_deplibs_check_method=pass_all ;;
This implies it's safe to link non-PIC into a shared library. Is this
really the case for sh? I'm not so sure. It's not just a matter of
the linker supporting it; the dynamic linker must as well.
Maybe, if all we need is to link libgcc into libstdc++.so et al, we
should take a similar approach to the one implemented by Zack for
hppa, that matches filenames with file_magic. See the patch he posted
on Apr 23.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}