From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH] meta-toolchain: use MULTIMACH_TARGET_SYS instead of TARGET_SYS
Date: Fri, 23 Apr 2010 16:54:39 -0400 [thread overview]
Message-ID: <20100423205439.GC27322@denix.org> (raw)
In-Reply-To: <hqt003$fvd$1@dough.gmane.org>
On Fri, Apr 23, 2010 at 10:29:54PM +0200, Koen Kooi wrote:
> >> Yes, that needs to be done, as well as seperating the cross tools in
> >> case different archs need different versions (as is the case with
> >> angstrom, v5te and v7a need different binutils). This change largely to
> >> to cosmetically highlight that the toolchain is not really "universal"
> >> (yet).
> >
> > And we can talk about if "universal" is really a good goal either.
>
> I don't think we can make it "universal" without sacrificing key benefits.
>
> > Taking a bit of a guess in the dark, an SDK with support for all the fun
> > stuff found on Beagleboard might not be done easily with also having
> > support for all the fun stuff found on some other ref board too.
>
> The immediate problem I'm trying to address now is that having both an
> armv5te and armv7a toolchain installed is breaking horribly. Ideally
> they would coexist peacefully, but I don't know if we can manage that,
> without impacting the ease of use.
I know it's not what you are looking for, but easier workaround would be to
install different toolchains in different paths... :)
--
Denys
next prev parent reply other threads:[~2010-04-23 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 12:21 [RFC][PATCH] meta-toolchain: use MULTIMACH_TARGET_SYS instead of TARGET_SYS Koen Kooi
2010-04-23 11:07 ` Koen Kooi
2010-04-23 18:07 ` Tom Rini
2010-04-23 18:22 ` Denys Dmytriyenko
2010-04-23 18:45 ` Koen Kooi
2010-04-23 18:55 ` Tom Rini
2010-04-23 20:29 ` Koen Kooi
2010-04-23 20:54 ` Denys Dmytriyenko [this message]
2010-04-23 21:43 ` Tom Rini
2010-04-24 17:07 ` Denys Dmytriyenko
2010-04-24 18:51 ` Tom Rini
2010-04-26 18:03 ` Denys Dmytriyenko
2010-04-27 18:18 ` Tom Rini
2010-04-30 19:35 ` Denys Dmytriyenko
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=20100423205439.GC27322@denix.org \
--to=denis@denix.org \
--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