From: Gary Thomas <gary@mlbassoc.com>
To: Chuck McManis <ecos@mcmanis.com>
Cc: ECOS Discussion Group <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Multiple GCC's, keeping them straight
Date: Sun, 23 Nov 2003 18:15:00 -0000 [thread overview]
Message-ID: <1069611346.25885.11.camel@hermes> (raw)
In-Reply-To: <6.0.0.22.2.20031123095424.02dedb20@66.125.189.29>
On Sun, 2003-11-23 at 10:59, Chuck McManis wrote:
> I'm being challenged by having multiple GCC tool chains around. It occurred
> to me that some readers might do this because they have multiple
> architectures to support and could thus offer some advice.
>
> What I'm trying to do is to have gcc 3.3.2 both 'native' and 'target' mode
> in my path. The goal is actually to have gcj (both 'native' and 'target')
> in my path so that I can compile Java code into my ECOS application.
>
> It hasn't been working particularly well, and I seem to get hung up in the
> binutils (either ld or perhaps gas) picking up the native one when I want
> the target one. Do folks run multiple chains in the same directory
> (differentiated by "gcc" vs "i386-elf-gcc" for example) or do they run with
> multiple paths and set those paths in Makefiles or something?
The most common case (and certainly how I manage it) is to use prefixed
compilers, e.g. i386-elf-gcc, etc. Trying to differentiate via paths is
bound to only cause you grief.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-11-23 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 17:59 Chuck McManis
2003-11-23 18:15 ` Gary Thomas [this message]
2003-11-24 10:11 ` Nick Garnett
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=1069611346.25885.11.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=ecos@mcmanis.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).