From: Ian Lance Taylor <ian@wasabisystems.com>
To: "Carl B. Constantine" <cconstan@csc.uvic.ca>
Cc: gcc-help@gcc.gnu.org
Subject: Re: compiling gcc for multiple targets?
Date: Wed, 31 Mar 2004 11:40:00 -0000 [thread overview]
Message-ID: <m31xn9fzoq.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20040330232033.GA1522@csc>
"Carl B. Constantine" <cconstan@csc.uvic.ca> writes:
> Is there any way to compile gcc and related utils (binutils, gdb) for
> multiple targets in one binary? So I want to compile it to support both
> Solaris intel and m68hc11 in one gcc instead of having separate binaries
> for each?
For gcc, no. For gas and gdb, sometimes. For the binutils and ld,
yes (use --enable-targets).
> If I cannot do this, but have to compile separate versions
> (--program-prefix=m6811-elf) are there any issues wrt to libraries if
> they are installed to the same place? libiberty.so for example?
libiberty.so is target independent, so it is safe to install the
libiberty.so for multiple targets in the same place. The target
libraries, such as libstdc++-v3, will by default be installed in
directories whose names depend upon the target, so they should not
ordinarily cause any conflicts. You should avoid building a shared
libbfd.so, as it will be target-dependent; that is, do not configure
the GNU binutils with --enable-shared.
Ian
next prev parent reply other threads:[~2004-03-31 3:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 8:17 Carl B. Constantine
2004-03-31 11:40 ` Ian Lance Taylor [this message]
2004-03-31 19:36 ` Ken Wolcott
2004-04-01 6:40 ` Bernd Jendrissek
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=m31xn9fzoq.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=cconstan@csc.uvic.ca \
--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).