public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: crossgcc@sources.redhat.com
Subject: Re: building gcc m68k-coff
Date: Thu, 12 Oct 2000 15:10:00 -0000	[thread overview]
Message-ID: <20001012200808.B577@tubul.dascon.de> (raw)
In-Reply-To: <20001011112440.H21675@aaron.frye.com>

On Wed, Oct 11, 2000 at 11:24:40AM -0700, Aaron J. Grier wrote:
> 
> another alternative is to use the "one tree" method of building, as
> shown in http://www.objsw.com/CrossGCC/FAQ-4.html#ss4.2 .  I have
> succesfully used the process to build m68k-rtems-elf, and m68k-elf, and
> a canadian cross for m68k-rtems-elf running on i386-cygwin.

I would also suggest going that way - I have successfully used it for
linux-hosted cross-compilers for m68k-coff, powerpc-eabi, sh-coff, and for
cross-compiling cygwin-to-sh/powerpc-compilers under linux.

The nice thing is that once you have everything set up, you get all the
needed tools in one go, with one simple command - building a new compiler
version or a compiler for a different target is quite easy then.

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

  reply	other threads:[~2000-10-12 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-11  9:53 ron tal
2000-10-11 11:25 ` Aaron J. Grier
2000-10-12 15:10   ` Michael Schwingen [this message]
2000-10-11 11:25 ron tal
2000-10-11 11:26 ron tal
2000-10-11 12:01 ` Aaron J. Grier

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=20001012200808.B577@tubul.dascon.de \
    --to=rincewind@discworld.dascon.de \
    --cc=crossgcc@sources.redhat.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).