From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] cross.bbclass: keep TARGET_SYS & TARGET_PREFIX independent.
Date: Thu, 20 Aug 2009 12:11:00 -0400 [thread overview]
Message-ID: <4A8D7594.4000606@cbnco.com> (raw)
In-Reply-To: <b6ebd0a50908200821r1cff2f42q4be6e8064abd76db@mail.gmail.com>
Chris Larson wrote:
>> Can you explain for a crosscompile noob -- when would TARGET_PREFIX !=
>> ${TARGET_SYS}-? I understand they're separate variables so they COULD be
>> different; just wondering why someone would set them that way.
>
> The only case that comes to mind is when using external toolchains.
> They aren't all so kind as to be arch-vendor-os-<foo>.
Cool, thanks for the explanation. For what it's worth,
Acked-by: Michael Smith <msmith@cbnco.com>
next prev parent reply other threads:[~2009-08-20 16:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 3:24 [PATCH] cross.bbclass: keep TARGET_SYS & TARGET_PREFIX independent Chris Larson
2009-08-20 3:24 ` [PATCH] patch.bbclass: catch exceptions raised in the Resolve() Chris Larson
2009-08-20 3:24 ` [PATCH] patch.bbclass: Add "git" patchtool mechanism, which uses git-apply Chris Larson
2009-08-20 3:24 ` [PATCH] kernel.bbclass: Set EXTRA_OEMAKE to null for kernel Chris Larson
2009-08-20 3:24 ` [PATCH] kernel.bbclass: Install & package symvers as /boot/Module.symvers-<ver> Chris Larson
2009-08-20 3:24 ` [PATCH] bitbake.conf: Kill CCACHE. Implicit, automatic use of things which can fail is bad Chris Larson
2009-08-20 3:24 ` [PATCH] bitbake.conf: Add export for cross NM Chris Larson
2009-08-20 3:24 ` [PATCH] bitbake.conf: BUILD_LDFLAGS: use $ORIGIN in the -rpath rather than a full path Chris Larson
2009-08-20 3:24 ` [PATCH] bitbake.conf: only pass --no-check-certificate if wget supports it Chris Larson
2009-08-20 4:18 ` [PATCH] bitbake.conf: BUILD_LDFLAGS: use $ORIGIN in the -rpath rather than a full path Denys Dmytriyenko
2009-08-20 4:53 ` Chris Larson
2009-08-20 5:06 ` Denys Dmytriyenko
2009-08-20 5:49 ` [PATCH] bitbake.conf: Add export for cross NM Holger Hans Peter Freyther
2009-08-20 4:06 ` [PATCH] bitbake.conf: Kill CCACHE. Implicit, automatic use of things which can fail is bad Denys Dmytriyenko
2009-08-20 5:49 ` Holger Hans Peter Freyther
2009-08-20 7:32 ` Graham Gower
2009-08-20 7:43 ` Denys Dmytriyenko
2009-08-20 12:09 ` Martyn Welch
2009-08-20 12:05 ` [PATCH] kernel.bbclass: Install & package symvers as /boot/Module.symvers-<ver> Michael Smith
2009-08-20 3:43 ` [PATCH] kernel.bbclass: Set EXTRA_OEMAKE to null for kernel Denys Dmytriyenko
2009-08-20 3:55 ` [PATCH] patch.bbclass: Add "git" patchtool mechanism, which uses git-apply Denys Dmytriyenko
2009-08-20 12:04 ` [PATCH] cross.bbclass: keep TARGET_SYS & TARGET_PREFIX independent Michael Smith
2009-08-20 15:21 ` Chris Larson
2009-08-20 16:11 ` Michael Smith [this message]
2010-02-25 18:28 ` Tom Rini
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=4A8D7594.4000606@cbnco.com \
--to=msmith@cbnco.com \
--cc=openembedded-devel@lists.openembedded.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