From: llewelly@xmission.com
To: Martin Baute <solar@rootdirectory.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Installing multiple GCC versions
Date: Tue, 27 Apr 2004 13:19:00 -0000 [thread overview]
Message-ID: <s3r7jw18sor.fsf@xmission.xmission.com> (raw)
In-Reply-To: <opr63l1iw443mbml@auth.mail.onlinehome.de>
Martin Baute <solar@rootdirectory.de> writes:
> Hi there,
>
> I'm using multiple configurations of binutils/GCC in parallel -
> Cygwin, MinGW, an i586-elf and a arm-wince cross compiler.
>
> I know my way around in a Unix environment, but the fine print
> of administering a system escapes me. Thus, so far my four
> compilers are scattered all over the filesystem. The preinstalled
> Cygwin and MinGW installations are in /usr, and the cross-
> compilers I installed in /usr/cross-elf and /usr/cross-arm
> using the "configure --prefix" option.
>
> This is unwieldly. I've seen the GCC "-b" option that apparently
> allows to specify the target machine in some kind of parallel
> GCC setup (as in "gcc -b i586-elf", if I understood it correctly),
> and would much prefer to enable that.
>
> But search as I might (including several Google's for "parallel
> GCC installation" or "cross-compiler parallel" or ...), I haven't
> found any guideline on how to add additional targets to an existing
> GCC installation.
>
> I see that target-specific directories should end up in /usr,
> where already /usr/i686-pc-cygwin and /usr/i686-pc-mingw32 reside.
> But if I just "configure --prefix=/usr --target=i586-elf", I would
> overwrite those parts of the existing installation that reside in
> /usr/bin and /usr/lib, no?
>
> How do I set up multiple parallel GCC installtions?
I use a different --prefix for each gcc install because I've had
strange behaviors from installing multiple gccs to the same
prefix.
I use a different --program-suffix for each gcc install so I can put
all of the bin directories in my path, and get the compiler I
want, without typing the full path to it.
I don't know if this is the best way. It's just what I do.
prev parent reply other threads:[~2004-04-27 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 4:41 Martin Baute
2004-04-27 13:19 ` llewelly [this message]
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=s3r7jw18sor.fsf@xmission.xmission.com \
--to=llewelly@xmission.com \
--cc=gcc-help@gcc.gnu.org \
--cc=solar@rootdirectory.de \
/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).