public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Mark Butcher <M_J_BUTCHER@compuserve.com>
Cc: gcc <gcc@gcc.gnu.org>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Tutorial 3
Date: Tue, 18 Jun 2002 16:56:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.30.0206181943300.88479-100000@dair.pair.com> (raw)
In-Reply-To: <200206181740_MC3-1-2E1-A114@compuserve.com>

On Tue, 18 Jun 2002, Mark Butcher wrote:

> I think that Bill Gatliff's site should be compulsory reading for anyone
> contemplating a GCC cross-build. [www.billgatliff.com]. Although there is
> only a relatively small amount of information, it is the information that
> is needed and the example script is even more or less understandable to a
> dummy like myself.
>
> Build BINUTILS
> Build a minimum gcc without headers and libraries
> Build NEWLIB with the minimum gcc
> Build the full GCC

Or build them all at once, with a unified tree.  Try
<URL:http://gcc.gnu.org/simtest-howto.html>: add "make install",
but strip dejagnu and gdb parts to taste.  Alternatively, using
tarballs with gcc, binutils and newlib instead of CVS, with
releases reasonably in phase, just untar them into the same
directory, then configure --target=..., make and make install.

The simulator targets (most of them) are actually bare-bones
*-elf cross-toolchains; the simulator is an add-on from the gdb
package.  Neccessary I/O libraries are built as part of the
newlib/libgloss package.

It's not rocket science.

brgds, H-P
PS.  Houston..?  Houston..?  ...darn, not again.

  reply	other threads:[~2002-06-18 23:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 14:41 Mark Butcher
2002-06-18 16:56 ` Hans-Peter Nilsson [this message]
2002-06-19 14:01 ` Peter Barada
  -- strict thread matches above, loose matches on Subject: below --
2002-06-18 14:41 Mark Butcher
2002-06-16 15:42 Mark Butcher
2002-06-17  1:57 ` Andrew Haley
2002-06-17  9:31 ` Peter Barada
2002-06-17 13:25 ` Phil Edwards

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=Pine.BSF.4.30.0206181943300.88479-100000@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=M_J_BUTCHER@compuserve.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@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).