From: Ralf Baechle <ralf@oss.sgi.com>
To: George Gensure <werkt@csh.rit.edu>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: Re: crti.o
Date: Fri, 25 May 2001 14:59:59 -0300 [thread overview]
Message-ID: <20010525145959.C1196@bacchus.dhis.org> (raw)
In-Reply-To: <3B0D990B.6090301@csh.rit.edu>; from werkt@csh.rit.edu on Thu, May 24, 2001 at 07:28:11PM -0400
On Thu, May 24, 2001 at 07:28:11PM -0400, George Gensure wrote:
> 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...
This file is part of the glibc package.
Ralf
next prev parent reply other threads:[~2001-05-25 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 23:28 crti.o George Gensure
2001-05-25 17:59 ` Ralf Baechle [this message]
-- 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=20010525145959.C1196@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=werkt@csh.rit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.