From: Ralf Jahr <ralf.jahr@informatik.uni-augsburg.de>
To: gcc-help@gcc.gnu.org
Subject: Trouble building cross-compiler i686-pc-linux-gnu => mipsel-elf
Date: Wed, 10 Sep 2008 09:37:00 -0000 [thread overview]
Message-ID: <48C7952D.8070508@informatik.uni-augsburg.de> (raw)
Dear list,
I try to build a cross-compiler for a mips-target. My goal is not to run
the code but to get an idea of how gcc performs optimizations as for
example modulo scheduling. The target I am actually working with is the
PISA architecture used by SimpleScalar. This is not supported but
similar to the mips4 architecture. So far...
I used this tutorial [1] and GCC 4.3.2, binutils 2.18. Compiling the
binutils and gcc worked fine, it did not throw any errors. You can see
my log here: [2]
[1] http://wiki.osdev.org/GCC_Cross-Compiler#Step_1_-_Bootstrap
[2] http://www.informatik.uni-augsburg.de/~jahrralf/gcc.php
Well, i assumed that I would get a compiler which can build executables.
Unfortunately but this does not work; I get the following error message:
/usr/cross-mips/lib/gcc/mipsel-elf/4.3.2/../../../../mipsel-elf/bin/ld:
crti.o: No such file: No such file or directory
collect2: ld returned 1 exit status
More logging information can be seen here:
http://www.informatik.uni-augsburg.de/~jahrralf/gcc.php#testing
Should this normally have worked? Do you have any ideas how in can make
it working or what I did wrong?
Thanks in advance, bye
Ralf
next reply other threads:[~2008-09-10 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 9:37 Ralf Jahr [this message]
2008-09-10 9:42 ` Andrew Haley
2008-09-10 13:48 ` Ralf Jahr
2008-09-10 13:52 ` John Love-Jensen
2008-09-10 14:43 ` Ralf Jahr
2008-09-10 22:25 ` Brian Dessent
2008-09-11 12:52 ` Ralf Jahr
2008-09-10 14:40 ` Kai Ruottu
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=48C7952D.8070508@informatik.uni-augsburg.de \
--to=ralf.jahr@informatik.uni-augsburg.de \
--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).