From: George Gensure <werkt@csh.rit.edu>
To: linux-mips <linux-mips@oss.sgi.com>
Subject: crti.o
Date: Thu, 24 May 2001 19:28:11 -0400 [thread overview]
Message-ID: <3B0D990B.6090301@csh.rit.edu> (raw)
Anyone know what the problem is when building the latest gcc when I get
a problem doing the final linking of the libgcc subdir? after listing a
whole bunch of object files, (not including crti.o) the linker errors
out, saying that it can't find crti.o. I've been muddling through this
for a while and just can't figure the problem out exactly...
George
werkt@csh.rit.edu
next reply other threads:[~2001-05-24 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 23:28 George Gensure [this message]
2001-05-25 17:59 ` crti.o Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
1997-04-30 22:01 crti.o Mike Shaver
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=3B0D990B.6090301@csh.rit.edu \
--to=werkt@csh.rit.edu \
--cc=linux-mips@oss.sgi.com \
/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