From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/3] Make multi-machine toolchains to co-exist.
Date: Sat, 24 Jul 2010 22:51:35 +0200 [thread overview]
Message-ID: <i2fjoo$iiu$1@dough.gmane.org> (raw)
In-Reply-To: <1279963975-3736-1-git-send-email-raj.khem@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 24-07-10 11:32, Khem Raj wrote:
> Hi
>
> Following three patches are for making multi-machine toolchains co-exist with
> new cross staging for toolchain.
>
> It changes the toolchain triplet from TARGET_ARCH-VENDOR-OS to TARGET_SUB_ARCH-VENDOR-OS
>
> which means that a toolchain for armv7 is called armv7-oe-linux-gnueabi-*
> and for armv5te its called armv5te-oe-linux-gnueabi-*
>
> They can coexist in same native sysroot. The symlinks would mean that
> gcc will not accidently mix the assemblers or linkers.
>
> I have booted a minimal-image on qemuarm successfully. The build for
> beagleboard in same sysroot is underway.
>
> Please give it a shot in your environments (especially Koen's env)
MACHINE=beagleboard bitbake nano ; MACHINE=hawkboard bitbake nano work,
going to try a bigger build now.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMS1JXMkyGM64RGpERAlZPAJ9q/D0n/slg4FfpvNVybcyscsfxWQCgulWl
9UWLPckdobpgJLGqWYTpt5k=
=jOIq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-24 20:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 9:32 [PATCH 0/3] Make multi-machine toolchains to co-exist Khem Raj
2010-07-24 9:32 ` [PATCH 1/3] bitbake.conf: Define HOST_SYS and TARGET_SYS based on target sub-arch Khem Raj
2010-07-24 9:32 ` [PATCH 2/3] binutils-cross.inc, binutils.inc: Overhaul for new cross dir structure Khem Raj
2010-07-24 9:32 ` [PATCH 3/3] gcc-cross: Use EXTRA_OECONF_PATHS in initial and intermediate recipes Khem Raj
2010-07-24 10:47 ` [PATCH 0/3] Make multi-machine toolchains to co-exist Koen Kooi
2010-07-24 20:51 ` Koen Kooi [this message]
2010-07-24 21:25 ` Khem Raj
2010-07-25 8:32 ` Koen Kooi
2010-07-25 11:16 ` Koen Kooi
2010-07-25 12:31 ` Koen Kooi
2010-07-25 14:41 ` Khem Raj
2010-07-25 15:10 ` Koen Kooi
2010-07-25 15:53 ` Richard Purdie
2010-07-25 19:43 ` Khem Raj
2010-07-26 7:50 ` Koen Kooi
2010-07-26 8:54 ` Khem Raj
2010-07-25 15:21 ` Richard Purdie
2010-07-25 14:30 ` Khem Raj
2010-07-25 15:19 ` Koen Kooi
2010-07-26 9:02 ` Eric Bénard
2010-07-26 9:01 ` Eric Bénard
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='i2fjoo$iiu$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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