From: Remy Fenn <rem@riscnx.net>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: ARM Configure Targets
Date: Thu, 06 Dec 2007 04:47:00 -0000 [thread overview]
Message-ID: <1196915510.1469.47.camel@blade> (raw)
In-Reply-To: <47574DD1.9000808@duaneellis.com>
On Thu, 2007-12-06 at 01:18, Duane Ellis wrote:
> Remy> Where can I find further information on specific [ARM] targets?
> You should learn about the "cross-gcc" mailing list.
>
> See this site for the archive: http://sourceware.org/ml/crossgcc/
>
> What is the _exact_ target (chip) you want?
> ie: A full arm-soc solution (like Xscale)
> or: A tiny arm7tdmi micro-controller type, with only 32K flash on
> chip?
>
> What is the _exact_ OS the board will run?
> ie: Roll your own
> or: Linux, great for Xscale, won't run on tiny micro-controllers.
> or: Some commercial thing, there are many.
> or: Something totally weirdo..
>
> Depending upon your answer, I might have something that will help you.
>
> -Duane.
I'm currently using a gcc configured for arm-elf which works fine for
cross-compiling Xscale software to run on embedded Debian.
I have raised this issue initially because I was unable to find an
official list of the specific configure targets which are available to
me when configuring gcc as a cross-compiler in this case for Arm/Linux
(purely out of curiousity). My particular problem is in understanding
why I should use arm-elf (which seems to be the defacto for a variety of
situations) rather than arm-linux or arm-linux-elf or arm-elf-linux or
whatever other combinations are currently available.
What are the supported configure targets, why does <blank> specific
target exist, how exactly does it differ from its relatives (e.g
arm-elf, arm-linux) and what benefits does it offer? These are questions
which have been burning inside me for a while now and I would be very
pleased if they could be answered if nothing else than for the sake of
my own sanity.
I'll go familiarise myself with crossgcc and see what I can come up
with.
Thanks.
--
Remy Fenn Email: rem@riscnx.net
Dept. Systems Engineering
Medway School of Engineering
The University of Greenwich
United Kingdom
next prev parent reply other threads:[~2007-12-06 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 1:18 Duane Ellis
2007-12-06 4:47 ` Remy Fenn [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-05 13:20 Remy Fenn
2007-12-05 15:21 ` Ian Lance Taylor
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=1196915510.1469.47.camel@blade \
--to=rem@riscnx.net \
--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).