From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/5][v4] Make multi-machine toolchains to co-exist (Alternate approach)
Date: Mon, 02 Aug 2010 11:33:42 +0200 [thread overview]
Message-ID: <i363dm$17p$1@dough.gmane.org> (raw)
In-Reply-To: <i31rhg$4a8$1@dough.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 31-07-10 20:54, Koen Kooi wrote:
> On 31-07-10 15:34, Koen Kooi wrote:
>> On 31-07-10 11:48, Koen Kooi wrote:
>>> On 31-07-10 07:34, Khem Raj wrote:
>>>> Hi
>
>>>> Following series of patches are for making multi-machine toolchains co-exist with
>>>> new cross staging for toolchain.
>
>>>> It installs the toolchain in <native sysroot>/usr/${BASE_PACKAGE_ARCH}
>>>> this way we can have multiple toolchains co-existing for different sub-arches and major arches too.
>
>>>> I have booted a native-sdk-image on qemuarm successfully. The build for
>>>> beagleboard minimal image using different versions of toolchain went all fine too.
>
>>>> Please test these patches and if seem ok provide some ACKS/NACKS
>
>>> Khem, thanks for working on this!
>
>>> Firing of a build now :)
>
>> 'MACHINE=beagleboard bitbake ffmpeg samba mysql5 gstreamer-ti' completed
>> succesfully, doing a 'MACHINE=hawkboard bitbake gtk+' now.
>
> And that seems to have worked as well. I have kicked of a huge
> multimachine build on the 16core buildserver at work and will inspect
> the results on monday. But so far it's looking really good.
The multimachine build finished as well. Before I ack this patch, are we
going to match the OE layout to the one used in poky?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMVpD2MkyGM64RGpERAsK8AJwMVi7zfHWt07AbegVk0MRvp4oMAgCaApKK
ADTLyDOwp79gCsVC1tV//mI=
=f9PZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-02 9:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 5:34 [PATCH 0/5][v4] Make multi-machine toolchains to co-exist (Alternate approach) Khem Raj
2010-07-31 5:34 ` [PATCH 1/5] bitbake.conf, cmake.bbclass, cross.bbclass, icecc.bbclass: Point the toolchain paths to new multi-machine friendly toolchain install location Khem Raj
2010-07-31 5:34 ` [PATCH 2/5] binutils-cross.inc: Dont install duplicate copies of tools create relative symlinks instead Khem Raj
2010-07-31 5:34 ` [PATCH 3/5] gcc, eglibc: Use the paths for mutli-machine safe toolchain install Khem Raj
2010-07-31 5:34 ` [PATCH 4/5] recipes: Fix the PATHs for toolchains Khem Raj
2010-07-31 5:34 ` [PATCH 5/5] mpfr_3.0.0.bb: Override needs to be thumb instead of armv4t Khem Raj
2010-07-31 9:48 ` [PATCH 0/5][v4] Make multi-machine toolchains to co-exist (Alternate approach) Koen Kooi
2010-07-31 13:34 ` Koen Kooi
2010-07-31 18:54 ` Koen Kooi
2010-08-02 9:33 ` Koen Kooi [this message]
2010-08-02 16:27 ` Khem Raj
2010-08-03 10:13 ` Koen Kooi
2010-08-03 10:21 ` Martin Jansa
2010-08-03 10:29 ` Andrea Adami
2010-08-03 10:31 ` Frans Meulenbroeks
2010-08-03 13:35 ` Martin Jansa
2010-08-03 15:36 ` Koen Kooi
2010-08-03 17:20 ` Khem Raj
2010-08-04 9:04 ` Martin Jansa
2010-08-03 19:58 ` Khem Raj
2010-08-03 19:56 ` Khem Raj
2010-08-01 15:48 ` 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='i363dm$17p$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