From: Michael Schwingen <rincewind@discworld.dascon.de>
To: Rolf.Barwick@aculab.com
Cc: crossgcc@sourceware.cygnus.com
Subject: Re: PowerPC Toolchain.
Date: Fri, 01 Dec 2000 02:38:00 -0000 [thread overview]
Message-ID: <20001201105358.A14559@a-tuin.dascon.de> (raw)
In-Reply-To: <0AEF0EB21F09D211AE4E0080C82733BF9D3F7D@mailhost.aculab.com>
On Thu, Nov 30, 2000 at 03:30:04PM -0000, Rolf.Barwick@aculab.com wrote:
> I wish to build a GNU Toolchain for a new PowerPC embedded system,
> using S-records. I am sure it can be done, though I run into tool building
> problems with the options I have used up to now.
> My questions:
> What --target= option should I be using for the configure script?
> Are there any special makefile targets which need to be specified
> for a cross compiler for generating low-level code? (That is I haven't yet
> written the OS libraries).
Look in the embedded-gcc FAQ on how to do a one-tree build of gcc, binutils
and newlib - using target powerpc-eabi, this works fine out of the box and
is the easiest way, even if you do not actually need newlib.
I am not sure if the linker can directly create s-records (but I think so) -
I usually let the linker generate an ELF file (with debug info), and then
use objcopy to convert that to S-records.
cu
Michael
--
Michael Schwingen, Ahornstrasse 36, 52074 Aachen
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-12-01 2:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 7:30 Rolf.Barwick
2000-12-01 2:38 ` Michael Schwingen [this message]
2000-12-01 5:24 ` Michael Schwingen
2000-12-01 7:18 ` Hans - Dulimarta
2000-11-30 7:50 David Korn
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=20001201105358.A14559@a-tuin.dascon.de \
--to=rincewind@discworld.dascon.de \
--cc=Rolf.Barwick@aculab.com \
--cc=crossgcc@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).