public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: [PATCH 1 of 2] docs: --target versus --host
Date: Wed, 16 Nov 2011 23:24:00 -0000	[thread overview]
Message-ID: <CAHUNapQcG+eY7w6gDyrBktLMtyf4fxC7ezPeTRPq9wG2_oRs3A@mail.gmail.com> (raw)
In-Reply-To: <201111170018.27492.yann.morin.1998@anciens.enib.fr>

Yann,

On Wed, Nov 16, 2011 at 6:18 PM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
>>  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...
>
> Aren't all these build/host/target things sneaky and confusing? ;-)
>
> To make things clear, I'd like to add this snippet:
>
>    (Note: in the above examples, 'host' refers to the host of your program,
>    not the host of the toolchain; and 'build' refers to the machine where
>    you build your program, that is the host of the toolchain.)
>
> What do you think?

Haha, yes! I sat there looking at it for a while and wondering which
would be correct :-)

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

  reply	other threads:[~2011-11-16 23:24 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 1 of 2] docs: --target versus --host Trevor Woerner
2011-11-16 23:18   ` Yann E. MORIN
2011-11-16 23:24     ` Trevor Woerner [this message]
2011-11-17 19:26     ` Thomas Petazzoni
2011-11-17 21:56       ` 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

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=CAHUNapQcG+eY7w6gDyrBktLMtyf4fxC7ezPeTRPq9wG2_oRs3A@mail.gmail.com \
    --to=twoerner@gmail.com \
    --cc=crossgcc@sourceware.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).