public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23687] Crosscompiler looks for files it never built
Date: Tue, 13 Sep 2005 07:50:00 -0000	[thread overview]
Message-ID: <20050913075047.15385.qmail@sourceware.org> (raw)
In-Reply-To: <20050901222628.23687.imipak@yahoo.com>


------- Additional Comments From rsandifo at gcc dot gnu dot org  2005-09-13 07:50 -------
Re crti.o and crtn.o: can I just check that you unpacked unmodified
FSF sources, configured with those arguments, ran "make", and that
"make" completed successfully, but that crti.o and crtn.o were
somehow not built?  If so, I'll need a log of the make process.

FWIW, many people build cross mips*-linux-gnu compilers, and I don't
remember ever hearing of this kind of problem before.  In case it helps
debugging, the rules to make crti.o and crtn.o are in config/mips/t-elf.

As discussed on the gcc lists, crt1.o and friends are provided
by glibc.

Using newlib for mips*-linux-gnu is basically unsupported.  I wouldn't
recommend trying it unless you're really keen on sorting through the
fallout yourself ;)

If you want us to look at the ICE, we'll need preprocessed
input.  Please see the bug-reporting instructions for details.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23687


  parent reply	other threads:[~2005-09-13  7:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01 22:26 [Bug c/23687] New: " imipak at yahoo dot com
2005-09-01 22:28 ` [Bug target/23687] " pinskia at gcc dot gnu dot org
2005-09-13  7:50 ` rsandifo at gcc dot gnu dot org [this message]
     [not found] <bug-23687-11278@http.gcc.gnu.org/bugzilla/>
2005-12-17  0:26 ` pinskia at gcc dot gnu dot org

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=20050913075047.15385.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).