This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [3.1] More regressions on S/390 - revert lib64 patch
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Alan Modra <amodra at bigpond dot net dot au>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 1 May 2002 04:44:25 -0400
- Subject: Re: [3.1] More regressions on S/390 - revert lib64 patch
- References: <OF811DA05C.CAFD7EAB-ONC1256BA7.006253B6@de.ibm.com> <20020427001207.GP31160@bubble.sa.bigpond.net.au>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Sat, Apr 27, 2002 at 09:42:07AM +0930, Alan Modra wrote:
> On Fri, Apr 26, 2002 at 09:01:31PM +0200, Ulrich Weigand wrote:
> > Due to this change, the start files (crti.o etc.) are now always used
> > from the absolute path given (/usr/lib/crti.o or /usr/lib64/crti.o).
>
> Since this has come up, I'll present my solution, a new spec to
> tweak default compiler search paths. Developed for powerpc64,
> but with x86_64, s390 etc. people in mind. x86_64 will be able
> to do something like:
>
> #define STARTFILE_PREFIX_SPEC "\
> %{m32: /usr/local/lib/ /lib/ /usr/lib/} \
> %{!m32: /usr/local/lib64/ /lib64/ /usr/lib64/}"
>
> and then get rid of those ugly absolute paths in STARTFILE_SPEC
> and ENDFILE_SPEC.
I like this, though I guess STARTFILE_PREFIX_SPEC should be used even
if native BI-ARCH compiler (e.g. sparc64-linux -> sparc64-linux which
supports both -m64 and -m32, similarly sparc-linux -> sparc-linux which
supports both -m32 and -m64).
Jakub