From: Jesper Skov <jskov@redhat.com>
To: Roman <RomanJordan@gmx.de>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] [Fwd: question about tools]
Date: Thu, 27 Jan 2000 03:46:00 -0000 [thread overview]
Message-ID: <ot66wflp0n.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <38900710.E2D3F2FF@gmx.de>
>Hi,
>i want to build a eCos System for my SA 1100 based ARM Board, with
>RedHat Host PC. (And later for my SH1 and SH2 boards also). But at the
>moment i have a lot of trouble by building. My Questions are:
>1. Can i use the egcs 1.1.2 compiler (arm-linux-gcc with elf output),
>which i used to generate a runninng linux kernel for the brutus board?
>Before i can do this, i have to change the file "pack....mak". But this
>not all. Some compiler and linker directives i have to change also. It
>is possible to build my own toolchain with the normal compiler and
>linker sources? Which is the target name for 'configure'? If i use
>arm-elf, i get 'arm-linux' (which can also produce elf output format).
configure --target=arm-elf
If that doesn't work the compiler probably doesn't have the necessary
support. I think the FAQ lists the minimum required compiler version -
I don't remember it off-hand.
>2. My linker don't know the option 'KEEP' within the linker script?
Then you need a newer version of the linker as well.
>3. Is there any eCos for Hitachi SH1 or SH2 available, and how can i
>generate the toolchain?
No. There's only support for SH3 at the moment. SH2 should be
possible to add support for, but SH1 will be a problem since there's
no g++ support for it (and as far as I know, no planned support for it
- which is a shame since I'd like to see eCos run on my brother's
LEGO MindStorm :)
Also, the SH3 support is only available in the early access program.
Jesper
next prev parent reply other threads:[~2000-01-27 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-27 0:47 Roman
2000-01-27 3:46 ` Jesper Skov [this message]
2000-01-27 8:01 ` Jesper Skov
2000-01-27 7:13 ` John M. Mills
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=ot66wflp0n.fsf@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=RomanJordan@gmx.de \
--cc=ecos-discuss@sourceware.cygnus.com \
/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).