Problem with sparc64-linux /usr/lib64 hardcoded

[Jakub Jelinek]

On Wed, Sep 06, 2000 at 10:27:07AM +0200, Andreas Jaeger wrote:
> 
> I've build a cross compiler from i686-linux to sparc64-linux to build
> glibc.  The specfile contains hardcoded the directory /usr/lib64 for
> e.g. crti.o.  This leads to the following failure building glibc:
> 
> /opt/sparc64-cross/lib/gcc-lib/sparc64-linux/2.96/../../../../sparc64-linux/bin/ld: cannot open /usr/lib64/crti.o: No such file or directory
> 
> Is there no other way than hardcoding /usr/lib64?  For example endfile
> has:
> *endfile:
> %{m32:%{!shared:crtend.o%s} %{shared:crtendS.o%s} crtn.o%s} %{m64:%{!shared:crtend.o%s} %{shared:crtendS.o%s} /usr/lib64/crtn.o%s} %{!m32:%{!m64:%{!shared:crtend.o%s} %{shared:crtendS.o%s} /usr/lib64/crtn.o%s}}
> 
> IMO we shouldn't use /usr/lib64 here - especially not in a cross-build
> with --prefix=/opt/sparc64-cross.  But how should it be handled?

Yes, this is a problem, see Geoff's message.
I just wanted to ask, are you using CVS gcc for sparc64 or Red Hat rawhide
rpm? If the former, then it will not work anyway, SUBREG_BYTE has not been
merged yet and there are a couple of sparc64 related patches in the rpm as
well.

	Jakub