From: "Ian S. Worthington" <ianworthington@usa.net>
To: <gcc-help@gcc.gnu.org>
Subject: make fails on ld: crti.o "no such file", but present in /usr/lib64
Date: Tue, 12 Feb 2008 17:47:00 -0000 [thread overview]
Message-ID: <931mBLRps8310S04.1202838423@cmsweb07.cms.usa.net> (raw)
Can anyone help me figure out what's wrong with this?
My "make bootstrap" of gcc 4.1.2 is failing with:
/usr/bin/ld: crti.o: No such file: No such file or directory
This file is available in /usr/lib64
In case it matters the final part of the log is:
.
.
.
libgcc/32/_udivmoddi4_s.o libgcc/32/unwind-dw2_s.o
libgcc/32/unwind-dw2-fde-glibc_s.o libgcc/32/unwind-sjlj_s.o
libgcc/32/gthr-gnat_s.o libgcc/32/unwind-c_s.o -lc && rm -f 32/libgcc_s.so &&
if [ -f 32/libgcc_s.so.1 ]; then mv -f 32/libgcc_s.so.1
32/libgcc_s.so.1.backup; else true; fi && mv 32/libgcc_s.so.1.tmp
32/libgcc_s.so.1 && ln -s libgcc_s.so.1 32/libgcc_s.so
/usr/bin/ld: crti.o: No such file: No such file or directory
collect2: ld returned 1 exit status
make[3]: *** [32/libgcc_s.so] Error 1
make[3]: Leaving directory `/ztpf/tpfcross/build/gcc'
make[2]: *** [stmp-multilib] Error 2
make[2]: Leaving directory `/ztpf/tpfcross/build/gcc'
make[1]: *** [stage1_build] Error 2
make[1]: Leaving directory `/ztpf/tpfcross/build/gcc'
make: *** [bootstrap] Error 2
and the configure command is:
/ztpf/tpfcross/source/gcc-4.1.2/configure
--prefix=/ztpf/tpfcross/install/native412 --enable-languages=c,c++
ian
...
Ian S. Worthington, MBCS.
http://isw.me.uk/
Dulce et decorum est pro patria mori, sed dulcius pro patria vivere, et
dulcissimus pro patria biber. Ergo, bibiamo pro salute patriae.
next reply other threads:[~2008-02-12 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 17:47 Ian S. Worthington [this message]
2008-02-12 17:59 ` Andrew Haley
2008-02-12 20:25 Ian S. Worthington
2008-02-12 20:39 ` Andrew Haley
2008-02-12 21:33 Ian S. Worthington
2008-02-13 11:37 ` Andrew Haley
2008-02-12 22:22 Poor Yorick
2008-02-13 0:14 Ian S. Worthington
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=931mBLRps8310S04.1202838423@cmsweb07.cms.usa.net \
--to=ianworthington@usa.net \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).