Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/8][v3] Make multi-machine toolchains to co-exist (revised again)
Date: Thu, 29 Jul 2010 19:44:22 +0200	[thread overview]
Message-ID: <i2selm$mrf$2@dough.gmane.org> (raw)
In-Reply-To: <1280213315-5513-1-git-send-email-raj.khem@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 27-07-10 08:48, Khem Raj wrote:
> Hi
> 
> Following series of 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_ARCH}-${CPU_SUB_TARGET}_${VENDOR}-OS
> 
> which means that a toolchain for armv7 is called arm-v7a_oe-linux-gnueabi-*
> and for armv5te its called arm-v5te_oe-linux-gnueabi-*
> 
> They can coexist in same native sysroot. The symlinks would mean that
> gcc will not accidently mix the assemblers or linkers.
> 
> MULTIMACH-* is not needed anymore as the TARGET_SYS is distinct enough
> to serve same purpose.
> 
> I have booted a minimal-image on qemuarm qemuppc and qemumips successfully. The build for 
> beagleboard native-sdk-image completed too.

So what's the status on this? The problem is still present in .dev, this
patchset introduces other problems and Phil & Richard want to take a
different approach.
Were do we go from here? I'd love to help out if I knew which approach
is the right one. I'm not fond of abusing TARGET_VENDOR, but if the
consensus is that's the way forward, so be it.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMUb31MkyGM64RGpERAtchAKCiNdy7Nbts/5fxA/wrUbrwZgpZRQCfcCcf
kcCkAByszubSkNi1H/ExBnU=
=UFfn
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-07-29 17:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27  6:48 [PATCH 0/8][v3] Make multi-machine toolchains to co-exist (revised again) Khem Raj
2010-07-27  6:48 ` [PATCH 1/8] bitbake.conf: Define HOST_SYS and TARGET_SYS based on target sub-arch Khem Raj
2010-07-27  6:48 ` [PATCH 2/8] binutils-cross.inc, binutils.inc: Overhaul for new cross dir structure Khem Raj
2010-07-27  6:48 ` [PATCH 3/8] gcc-cross: Use EXTRA_OECONF_PATHS in initial and intermediate recipes Khem Raj
2010-07-27  6:48 ` [PATCH 4/8] sdk.bbclass: override BASEPKG_HOST_SYS as it is used to make TARGET_SYS Khem Raj
2010-07-27  6:48 ` [PATCH 5/8] machines: Add new variable TARGET_SUB_ARCH Khem Raj
2010-07-27  6:48 ` [PATCH 6/8] classes, bitbake.conf: Add MACHINE_SYS and CURRENT_TARGET_SYS Khem Raj
2010-07-27  6:48 ` [PATCH 7/8] recipes: Replace usage of MULTIMACH_TARGET_SYS with CURRENT_TARGET_SYS Khem Raj
2010-07-27  6:57   ` Koen Kooi
2010-07-27  9:12     ` Khem Raj
2010-07-27  6:48 ` [PATCH 8/8] recipes: Replace ${PN} override with pn-${PN} for PACKAGE_ARCH Khem Raj
2010-07-27  6:55   ` Koen Kooi
2010-07-27  7:32   ` Phil Blundell
2010-07-28  7:07 ` [PATCH 0/8][v3] Make multi-machine toolchains to co-exist (revised again) Koen Kooi
2010-07-28 17:25   ` Khem Raj
2010-07-29 17:44 ` Koen Kooi [this message]
2010-07-29 17:53   ` Khem Raj

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='i2selm$mrf$2@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