From: Doug Evans <dje@transmeta.com>
To: "Moore, Jason" <Jason_Moore@gilbarco.com>
Cc: "'JAY LULLA'" <JAY.LULLA@Sun.COM>,
crossgcc@sourceware.cygnus.com, gcc-help@gcc.gnu.org
Subject: RE: Installing cross-compiler for PowerPC 603, pSOS
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <14463.37927.758174.322793@casey.transmeta.com> (raw)
Message-ID: <20000401000000.CapuyZHUDmku8kDk3hiTugwxyN7_hdIfKJmJmY-OuHE@z> (raw)
In-Reply-To: <200001142049.PAA24692@hoover.gilbarco.com>
Moore, Jason writes:
> >Here are some issues I need to address:
> >- should the cross-compiler be installed in the same dir as the native
> >compiler, and then be called with a special flag, or should it be
> >installed in a whole new directory altogether?
>
> I believe that it has to me installed in a separate directory, but I am not
> sure. Everything I have read suggest that you must have 2 separate
> compilers. One native, and one cross. One solution is to create a script
> that can determine which version to use.
They _can_ be installed in the same directory (if by same directory you
mean same value for --prefix). gcc for the native host is named "gcc".
gcc for the target by default is named "${target_alias}-gcc".
> You can install binutils in the same place as your other binutils, where
> "ld" currently sits, but you must be sure to configure it for both your
> target and host emulation modes, or else you'll have a linker that only does
> one or the other. Running the binutils "configure" with the
> "--enable-targets='target','host'" will accomplish this.
Methinks you've got things confused a tad.
There's no need to specify --enable-targets for the task at hand.
Certainly you don't need a linker that handles both host and target.
As with gcc, non-native versions of as,ld,objdump,etc. get installed
as ${target_alias}-{ad,ld,objdump,etc.}. e.g. if you've configured
binutils for powerpc-eabi then you'll get powerpc-eabi-ld, etc.
Note however that these versions of as,ld are not what gcc uses.
${target_alias}-ld is for the user should s/he ever want to call it
directly. A copy of the target linker is installed in (assuming prefix
specified and exec-prefix isn't) $prefix/$target_alias/bin, and this
is what gcc uses.
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-14 12:50 Moore, Jason
2000-01-14 13:25 ` Doug Evans [this message]
2000-04-01 0:00 ` Doug Evans
2000-04-01 0:00 ` Moore, Jason
-- strict thread matches above, loose matches on Subject: below --
2000-01-14 11:35 JAY LULLA
2000-04-01 0:00 ` JAY LULLA
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=14463.37927.758174.322793@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=JAY.LULLA@Sun.COM \
--cc=Jason_Moore@gilbarco.com \
--cc=crossgcc@sourceware.cygnus.com \
--cc=gcc-help@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).