This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
I think all are ok.
What you need do is to add the new target item in configure.in and other files with right specification.
To: gcc@gcc.gnu.org
cc: elug@linux.ab.ca
(bcc: Qinfeng Zhang/SHA/RESEARCH/PHILIPS)
Subject: Cross Compiling, Target String, etc...
Jakub Sadowski
<jakubsadowski@yahoo.com Classification:
>
Sent by:
gcc-owner@gcc.gnu.org
2003-06-18 12:12
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?
=====
- Jakub Sadowski
--
"The philosophy of one century is the common sense of the next." - Anonymous
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |