From: Denys Dmytriyenko <denys@ti.com>
To: Flavio Castro Alves Filho <flavio.alves@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: Help with building gstreamer-ti on beagleboard
Date: Tue, 13 Nov 2012 20:37:51 -0500 [thread overview]
Message-ID: <20121114013751.GB13096@edge> (raw)
In-Reply-To: <CAFNBftdZC1BUCUA+zonbgkFshzft=ba=BYyTBKFKTXBOo_DVsA@mail.gmail.com>
On Tue, Nov 13, 2012 at 11:10:31PM -0200, Flavio Castro Alves Filho wrote:
> 2012/11/13 Tomas Frydrych <tf+lists.yocto@r-finger.com>
>
> | make[1]: /arm-poky-linux-gnueabi-gcc: Command not found
^^^^^^^^^
Yes, some of the recipes in meta-ti still use old TOOLCHAIN_* vars from
Classic OE, which were set specifically to allow building packages either
with an internal toolchain or with an external prebuilt one. In OE-Core or
Yocto/Poky those vars are not set by default, as it's left for the
distribution to deal with setting up any fancy toolchain business. You'd
need to add something like this to your config file:
TOOLCHAIN_PATH ?= "${STAGING_BINDIR_TOOLCHAIN}"
TOOLCHAIN_SYSPATH ?= "${TOOLCHAIN_PATH}/${TARGET_SYS}"
--
Denys
next prev parent reply other threads:[~2012-11-14 1:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 13:46 Help with building gstreamer-ti on beagleboard Flavio Castro Alves Filho
2012-11-13 15:15 ` Tomas Frydrych
2012-11-13 15:22 ` Denys Dmytriyenko
2012-11-13 15:38 ` Tomas Frydrych
2012-11-13 15:43 ` Robert P. J. Day
2012-11-13 15:44 ` Denys Dmytriyenko
2012-11-13 21:25 ` Flavio Castro Alves Filho
2012-11-13 21:51 ` Tomas Frydrych
2012-11-14 1:10 ` Flavio Castro Alves Filho
2012-11-14 1:37 ` Denys Dmytriyenko [this message]
2012-11-14 6:19 ` Flavio Castro Alves Filho
2012-11-14 18:09 ` Flavio Castro Alves Filho
2012-11-15 13:29 ` Flavio Castro Alves Filho
2012-11-14 1:28 ` 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=20121114013751.GB13096@edge \
--to=denys@ti.com \
--cc=flavio.alves@gmail.com \
--cc=meta-ti@yoctoproject.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.