From: "Rupert Wood" <me@rupey.net>
To: <sarae@hss.hns.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: How to build cross compiler
Date: Fri, 28 Jun 2002 02:21:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D561703@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D6BF9BB@whale.softwire.co.uk>
Samant wrote:
> I want to build a cross compiler which runs on Red Hat 6.2 -- intel
> and generates executables which are run on target Red Hat 6.2 --
> powerpc.
>
> Please suggest me some documents for this... FAQs ?
FAQ and CrossGCC mailing list archives:
http://crossgcc.billgatliff.com/
http://sources.redhat.com/ml/crossgcc/
> I think, i need to build :
0) Binutils with --target=powerpc-linux. You may combine this with step
1 by creating a merged source tree, e.g. as described
http://gcc.gnu.org/simtest-howto.html
If built separately then you need to install these before you continue.
They should be built with the same --prefix that you're going to
build/install GCC to.
> 1) Gcc with --target=powerpc-linux
> 2) Glibc with gcc obtained in step 1.
or if you have access to powerpc-linux system headers and libraries (and
you're willing to use them rather than rebuilding glibc - probably a
good idea if you have an existing system in mind) then you can copy
these to <prefix>/powerpc-linux/sys-include and
<prefix>/powerpc-linux/lib and skip these two steps. This will be
described in the CrossGCC FAQ.
> 3) Gcc with Glibc obtained in step 2
Good luck,
Rup.
next parent reply other threads:[~2002-06-28 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18D6BF9BB@whale.softwire.co.uk>
2002-06-28 2:21 ` Rupert Wood [this message]
2002-06-27 20:22 sarae
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=616BE6A276E3714788D2AC35C40CD18D561703@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=gcc-help@gcc.gnu.org \
--cc=sarae@hss.hns.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).