From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] ti-dsplink: Fixed location of toolchain
Date: Tue, 14 Jun 2011 15:31:17 -0400 [thread overview]
Message-ID: <20110614193117.GD1324@denix.org> (raw)
In-Reply-To: <it7vpr$n45$1@dough.gmane.org>
On Tue, Jun 14, 2011 at 05:47:07PM +0200, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 14-06-11 17:38, Denys Dmytriyenko wrote:
> > On Tue, Jun 14, 2011 at 09:36:26AM +0200, Koen Kooi wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> On 14-06-11 05:55, Joel A Fernandes wrote:
> >>> ti-dsplink: Fixed location of toolchain to build ti-dsplink.
> >>
> >> It sadly really needs an absolute path to the tools :(
> >
> > So, what was this patch trying to fix anyway? Is there something broken?
>
> Using an external toolchain without your import magic and then
> overriding TOOLCHAINPATH in local.conf is broken. You might call it
> broken by design :)
As you know, the design is hindered by requirements, so ease up! :)
As of the "import magic" - there is nothing magical about it, it just sets up
TOOLCHAIN_PATH and TOOLCHAIN_SYSPATH automatically. Otherwise you'd have to
set at least TOOLCHAIN_PATH manually and it works. So, I still don't see what
exactly is broken and needs to be fixed.
BTW, the requirements for absolute toolchain path come from dsplink and not
the external toolchain, AFAICR...
--
Denys
next prev parent reply other threads:[~2011-06-14 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 3:55 [PATCH] ti-dsplink: Fixed location of toolchain Joel A Fernandes
2011-06-14 5:51 ` Denys Dmytriyenko
2011-06-14 7:36 ` Koen Kooi
2011-06-14 15:38 ` Denys Dmytriyenko
2011-06-14 15:47 ` Koen Kooi
2011-06-14 19:31 ` Denys Dmytriyenko [this message]
2011-06-14 19:38 ` Koen Kooi
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=20110614193117.GD1324@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.