public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Installing multiple GCC versions
@ 2004-04-27  4:41 Martin Baute
  2004-04-27 13:19 ` llewelly
  0 siblings, 1 reply; 2+ messages in thread
From: Martin Baute @ 2004-04-27  4:41 UTC (permalink / raw)
  To: gcc-help

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?

Many thanks in advance,
--
Martin Baute
solar@rootdirectory.de

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Installing multiple GCC versions
  2004-04-27  4:41 Installing multiple GCC versions Martin Baute
@ 2004-04-27 13:19 ` llewelly
  0 siblings, 0 replies; 2+ messages in thread
From: llewelly @ 2004-04-27 13:19 UTC (permalink / raw)
  To: Martin Baute; +Cc: gcc-help

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-04-27 13:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-27  4:41 Installing multiple GCC versions Martin Baute
2004-04-27 13:19 ` llewelly

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).