This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Cross Compiling, Target String, etc...
- From: Michael Eager <eager at eagercon dot com>
- To: Jakub Sadowski <jakubsadowski at yahoo dot com>
- Cc: gcc at gcc dot gnu dot org, elug at linux dot ab dot ca
- Date: Thu, 19 Jun 2003 10:14:10 -0700
- Subject: Re: Cross Compiling, Target String, etc...
- References: <20030618041239.82666.qmail@web11607.mail.yahoo.com>
Jakub Sadowski wrote:
Cross-Compiling...man what confusion...
What is the significance of the host string that follows target=<host> (sometimes
CROSS_COMPILE=<host>)? It's format is <CPU>-<BRAND>-<KERNEL>-<OS>. I've checked glibc-2.3.1 and
it WILL NOT matter what you place for <BRAND> (see glibc-2.3.1/INSTALL, under supported
configurations). Is there any rhyme or reason for this naming scheme? How do I predict what a
host string should be? i.e. I want to compile for a Celeron based pc running linux. What's my
<HOST> string? i686-pc-linux-gnu? x86-unknown-linux? Celeron-outdatedworkstation-linux-gnu?
There is a rhyme and reason to the naming scheme. Or, perhaps, a variety of different
rhymes and reasons, depending on who added the target triple to gcc and other packages.
Sometimes a triple which works with one package will not be accepted by another.
As you noticed, most packages ignore BRAND, or only use it sporadically.
Take a look at config.gcc to see what triples are defined. Pick one which looks
reasonable. In your situation, i686-pc-linux-gnu would appear appropriate.
--
Michael Eager Eager Consulting eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077