This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Problem with sparc64-linux /usr/lib64 hardcoded
- To: gcc-bugs at gcc dot gnu dot org
- Subject: Problem with sparc64-linux /usr/lib64 hardcoded
- From: Andreas Jaeger <aj at suse dot de>
- Date: 06 Sep 2000 10:27:07 +0200
- Cc: Jakub Jelinek <jakub at redhat dot com>
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?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj