From: Daniel Jacobowitz <drow@false.org>
To: Kevin Handy <kth@srv.net>
Cc: gcc@gcc.gnu.org
Subject: Re: armv4t
Date: Mon, 21 Sep 2009 17:59:00 -0000 [thread overview]
Message-ID: <20090921175935.GA24378@caradoc.them.org> (raw)
In-Reply-To: <4AB7BDC9.1060701@srv.net>
On Mon, Sep 21, 2009 at 11:54:17AM -0600, Kevin Handy wrote:
> What version of GCC will build for a cross --target=armv4t-linux-eabi,
> which I believe is the right code for an ixp425 processor? The host
> compiler is gcc-4.3.3 on a Linux-debian-test system. I have also tried
> unsuccessfully tried the armv5t target, with similar results.
Don't try to put it in the triplet. Try using --with-cpu instead, and
a normal armv4t-linux-gnueabi triplet.
I'm pretty sure Xscale implements ARM v5TE though, so none of thse
hoops should be necessary.
> I need to find out where to look for a functional version of the gcc
> cross compiler for this cpu.
If you can't build GCC for your target, I suggest you either use a
help list for that purpose (gcc-help or the crosstool or buildroot
lists), or find a pre-compiled ARM Linux toolchain.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-09-21 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 17:54 armv4t Kevin Handy
2009-09-21 17:59 ` Daniel Jacobowitz [this message]
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=20090921175935.GA24378@caradoc.them.org \
--to=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=kth@srv.net \
/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).