public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: [PATCH 1 of 2] docs: --target versus --host
Date: Wed, 16 Nov 2011 22:46:00 -0000	[thread overview]
Message-ID: <c1c4d9174fbfd7d76e0e.1321483526@codei7.fpelectronics.com> (raw)
In-Reply-To: <patchbomb.1321483525@codei7.fpelectronics.com>

# HG changeset patch
# User Trevor Woerner <twoerner@gmail.com>
# Date 1321477602 18000
# Node ID c1c4d9174fbfd7d76e0e520dc6657cf239a7d718
# Parent  c4452a1a18fb5c57b991eb75f7ff480d33e91704
docs: --target versus --host

In the very beginnings, eons ago, autotools also got confused by this
whole build vs. host vs. target, and got it wrong. Now they fixed it,
but they want to keep backward compatibility, so the --target is still
recongised, although ./configure will complain if you do so. It is
better to use --host.

Signed-off-by: "Trevor Woerner" <twoerner@gmail.com>

diff -r c4452a1a18fb -r c1c4d9174fbf docs/5 - Using the toolchain.txt
--- a/docs/5 - Using the toolchain.txt	Tue Nov 15 19:11:57 2011 +0100
+++ b/docs/5 - Using the toolchain.txt	Wed Nov 16 16:06:42 2011 -0500
@@ -11,13 +11,14 @@
 your PATH, such as:
   export PATH="${PATH}:/your/toolchain/path/bin"
 
-and then using the target tuple to tell the build systems to use your
-toolchain:
-  ./configure --target=your-target-tuple
+and then using the '--host' tuple to tell the build systems to use your
+toolchain (if the software package uses the autotools system you should
+also pass --build, for completeness):
+  ./configure --host=your-host-tuple --build=your-build-tuple
 or
-  make CC=your-target-tuple-gcc
+  make CC=your-host-tuple-gcc
 or
-  make CROSS_COMPILE=your-target-tuple-
+  make CROSS_COMPILE=your-host-tuple-
 and so on...
 
 It is strongly advised not to use the toolchain sysroot directory as an

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  parent reply	other threads:[~2011-11-16 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 22:46 [PATCH 0 of 2] documentation update Trevor Woerner
2011-11-16 22:46 ` [PATCH 2 of 2] docs: Add strategies for assembling root filesystems Trevor Woerner
2011-11-16 23:29   ` Yann E. MORIN
2011-11-17 19:29     ` Thomas Petazzoni
2011-11-17 20:15       ` David Wuertele
2011-11-17 20:32         ` Thomas Petazzoni
2011-11-17 23:05       ` Trevor Woerner
2011-11-16 22:46 ` Trevor Woerner [this message]
2011-11-16 23:18   ` [PATCH 1 of 2] docs: --target versus --host Yann E. MORIN
2011-11-16 23:24     ` Trevor Woerner
2011-11-17 19:26     ` Thomas Petazzoni
2011-11-17 21:56       ` Trevor Woerner

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=c1c4d9174fbfd7d76e0e.1321483526@codei7.fpelectronics.com \
    --to=twoerner@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=yann.morin.1998@anciens.enib.fr \
    /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).