Help with building gstreamer-ti on beagleboard

Help with building gstreamer-ti on beagleboard

[Flavio Castro Alves Filho]

[-- Attachment #1: Type: text/plain, Size: 6512 bytes --]

Hello all,

I'm using Yocto Project and meta-ti to build an embedded Linux distribution
for BeagleBoard-xM.

I need to add gstreamer-ti into the project, and I'm having problems in
building this package with my configuration.

Here is the messages:

flavio@buildstation:/home/prjs/tk0001/philinux/philinux-beagleboard$
bitbake gstreamer-ti
WARNING: Host distribution "Ubuntu 12.04.1 LTS" has not been validated with
this version of the build system; you may possibly experience unexpected
failures. It is recommended that you use a tested distribution.
WARNING:
/home/prjs/tk0001/philinux/meta-openembedded/meta-oe/recipes-connectivity/networkmanager/
networkmanager_0.9.2.0.bb: it is recommended to set SYSTEMD_PACKAGES as
<existing-package>-systemd
WARNING: /home/prjs/poky/meta/recipes-extended/lighttpd/lighttpd_1.4.30.bb:
it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd0:01
Parsing recipes: 100%
|################################################################################################################|
Time: 00:00:53
Parsing of 1216 .bb files complete (0 cached, 1216 parsed). 1545 targets,
48 skipped, 7 masked, 0 errors.

OE Build Configuration:
BB_VERSION        = "1.15.2"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beagleboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.2.1"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto        =
"local/origin/denzil:73cdebf60df225ee10f2eb215935be3b61e1b831"
meta-ti           =
"local/origin/denzil:9c103ce85a6ecb836bcdc46137207e466846ee2e"
meta-oe           =
"local/origin/denzil:6e434777018b81bbd7873e7278f05425de18558a"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 778 of 1629 (ID: 587,
/home/prjs/tk0001/philinux/meta-ti/recipes-ti/devtools/
ti-xdctools_3.23.00.32.bb, do_patch)
NOTE: Running task 857 of 1629 (ID: 578,
/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/
ti-codec-engine_2.26.02.11.bb, do_fetch)
NOTE: package ti-xdctools-3_23_00_32-r0: task do_patch: Started
NOTE: package ti-codec-engine-2_26_02_11-${MACHINE_KERNEL_PR}b: task
do_fetch: Started
ERROR: Error executing a python function in
/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/
ti-codec-engine_2.26.02.11.bb:
ExpansionError: Failure expanding variable FILESPATH, expression was
${@base_set_filespath([
"/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/ti-codec-engine-2_26_02_11-${MACHINE_KERNEL_PR}b",
"/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/ti-codec-engine-2_26_02_11",
"/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/ti-codec-engine",
"/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/ti-codec-engine-2_26_02_11",
"/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/ti-codec-engine",
"/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/files",
"/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine" ], d)} which
triggered exception SyntaxError: EOL while scanning string literal
(FILESPATH, line 1)

ERROR: The stack trace of python calls that resulted in this
exception/failure was:
ERROR:   File "base_do_fetch", line 18, in <module>
ERROR:
ERROR:   File "base_do_fetch", line 13, in base_do_fetch
ERROR:
ERROR:   File "/home/prjs/poky/bitbake/lib/bb/fetch2/__init__.py", line
946, in download
ERROR:     ud.setup_localpath(self.d)
ERROR:
ERROR:   File "/home/prjs/poky/bitbake/lib/bb/fetch2/__init__.py", line
621, in setup_localpath
ERROR:     self.localpath = self.method.localpath(self.url, self, d)
ERROR:
ERROR:   File "/home/prjs/poky/bitbake/lib/bb/fetch2/local.py", line 54, in
localpath
ERROR:     filespath = data.getVar('FILESPATH', d, True)
ERROR:
ERROR:   File "/home/prjs/poky/bitbake/lib/bb/data.py", line 89, in getVar
ERROR:     return d.getVar(var, exp)
ERROR:
ERROR:   File "/home/prjs/poky/bitbake/lib/bb/data_smart.py", line 282, in
getVar
ERROR:     return self.expand(value, var)
ERROR:
ERROR:   File "/home/prjs/poky/bitbake/lib/bb/data_smart.py", line 151, in
expand
ERROR:     return self.expandWithRefs(s, varname).value
ERROR:
ERROR:   File "/home/prjs/poky/bitbake/lib/bb/data_smart.py", line 141, in
expandWithRefs
ERROR:     raise ExpansionError(varname, s, exc)
ERROR:
ERROR: The code that was being executed was:
ERROR:      0014:        except bb.fetch2.BBFetchException, e:
ERROR:      0015:            raise bb.build.FuncFailed(e)
ERROR:      0016:
ERROR:      0017:
ERROR:  *** 0018:base_do_fetch(d)
ERROR:      0019:
ERROR: (file: 'base_do_fetch', lineno: 18, function: <module>)
ERROR:      0009: bb.data.update_data(localdata)
ERROR:      0010:
ERROR:      0011:        try:
ERROR:      0012:            fetcher = bb.fetch2.Fetch(src_uri, localdata)
ERROR:  *** 0013:            fetcher.download()
ERROR:      0014:        except bb.fetch2.BBFetchException, e:
ERROR:      0015:            raise bb.build.FuncFailed(e)
ERROR:      0016:
ERROR:      0017:
ERROR: (file: 'base_do_fetch', lineno: 13, function: base_do_fetch)
ERROR: Function failed: base_do_fetch
ERROR: Logfile of failure stored in:
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-codec-engine-2_26_02_11-${MACHINE_KERNEL_PR}b/temp/log.do_fetch.26599
NOTE: package ti-codec-engine-2_26_02_11-${MACHINE_KERNEL_PR}b: task
do_fetch: Failed
ERROR: Task 578 (/home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/
ti-codec-engine_2.26.02.11.bb, do_fetch) failed with exit code '1'
Waiting for 1 running tasks to finish:
0: ti-xdctools-3_23_00_32-r0 do_patch (pid 26598)
NOTE: package ti-xdctools-3_23_00_32-r0: task do_patch: Succeeded
NOTE: Tasks Summary: Attempted 857 tasks of which 855 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
  /home/prjs/tk0001/philinux/meta-ti/recipes-ti/codec-engine/
ti-codec-engine_2.26.02.11.bb, do_fetch
Summary: There were 3 WARNING messages shown.
Summary: There were 46 ERROR messages shown, returning a non-zero exit code.

Does anybody have any clue about how to solve this issue?

Best regards,

Flavio

-- 
Flavio de Castro Alves Filho

flavio.alves@gmail.com
www.linuxembarcado.com
Twitter: http://twitter.com/#!/fraviofii
LinkedIn profile: www.linkedin.com/in/flaviocastroalves

[-- Attachment #2: Type: text/html, Size: 8550 bytes --]

Re: Help with building gstreamer-ti on beagleboard

[Tomas Frydrych]

Hi,

On 13/11/12 13:46, Flavio Castro Alves Filho wrote:
> Hello all,
> 
> I'm using Yocto Project and meta-ti to build an embedded Linux distribution
> for BeagleBoard-xM.
> 
> I need to add gstreamer-ti into the project, and I'm having problems in
> building this package with my configuration.
> 
> NOTE: package ti-codec-engine-2_26_02_11-${MACHINE_KERNEL_PR}b: task
> do_fetch: Started

My guess would be that your layers are not set up correctly, you can see
in the error output that the ${MACHINE_KERNEL_PR} variable is not
getting expanded; this is defined in omap3.inc in meta-ti, which would
be included from the meta-ti beagleboard.conf, but the way the layers
are set up leads to the yocto beagleboard.conf being used instead.

For Denzil it is not possible to arrange meta-yocto and meta-ti layers
in a way that would work; this has been fixed in Danny (in
meta-yocto-bsp). If you want to stick with Denzil, there are different
ways to work around it, easiest should be to delete the offending
beagleboard.conf from meta-yocto.

(If you are providing your own distro layer, and the layer is set up to
prefix itself to the BBPATH, you can provide your own beagleboard.conf
that sources the correct one from meta-ti, something like this,
https://github.com/Guacamayo/meta-guacamayo/blob/master/meta-guacamayo/conf/machine/beagleboard.conf).

Tomas

Re: Help with building gstreamer-ti on beagleboard

[Denys Dmytriyenko]

On Tue, Nov 13, 2012 at 03:15:28PM +0000, Tomas Frydrych wrote:
> Hi,
> 
> On 13/11/12 13:46, Flavio Castro Alves Filho wrote:
> > Hello all,
> > 
> > I'm using Yocto Project and meta-ti to build an embedded Linux distribution
> > for BeagleBoard-xM.
> > 
> > I need to add gstreamer-ti into the project, and I'm having problems in
> > building this package with my configuration.
> > 
> > NOTE: package ti-codec-engine-2_26_02_11-${MACHINE_KERNEL_PR}b: task
> > do_fetch: Started
> 
> My guess would be that your layers are not set up correctly, you can see
> in the error output that the ${MACHINE_KERNEL_PR} variable is not
> getting expanded; this is defined in omap3.inc in meta-ti, which would
> be included from the meta-ti beagleboard.conf, but the way the layers
> are set up leads to the yocto beagleboard.conf being used instead.

Right.


> For Denzil it is not possible to arrange meta-yocto and meta-ti layers
> in a way that would work; this has been fixed in Danny (in
> meta-yocto-bsp). If you want to stick with Denzil, there are different
> ways to work around it, easiest should be to delete the offending
> beagleboard.conf from meta-yocto.

Why can't you put meta-ti in front of meta-yocto in Denzil? Works just fine.


> (If you are providing your own distro layer, and the layer is set up to
> prefix itself to the BBPATH, you can provide your own beagleboard.conf
> that sources the correct one from meta-ti, something like this,

Well, it's only the problem for the BBLAYERS order, so you don't really need 
any fancy setups, just do this in build/conf/bblayers.conf in Denzil:

BBLAYERS ?= " \
  /OE/poky/meta \
  /OE/poky/meta-ti \
  /OE/poky/meta-yocto \
  "

Or for Danny/master:

BBLAYERS ?= " \
  /OE/poky/meta \
  /OE/poky/meta-yocto \
  /OE/poky/meta-ti \
  /OE/poky/meta-yocto-bsp \
  "

-- 
Denys

Re: Help with building gstreamer-ti on beagleboard

[Tomas Frydrych]

On 13/11/12 15:22, Denys Dmytriyenko wrote:
>> For Denzil it is not possible to arrange meta-yocto and meta-ti layers
>> in a way that would work; this has been fixed in Danny (in
>> meta-yocto-bsp). If you want to stick with Denzil, there are different
>> ways to work around it, easiest should be to delete the offending
>> beagleboard.conf from meta-yocto.
> 
> Why can't you put meta-ti in front of meta-yocto in Denzil? Works just fine.

Because meta-yocto layer.conf does:

  BBPATH := "${LAYERDIR}:${BBPATH}"

While meta-ti layer.conf does:

  BBPATH .= ":${LAYERDIR}"

So regardless how you order it, you get BBPATH that looks like:

  meta-yocto:meta:meta-ti

Which guarantees you the beagleboard.conf from meta-yocto.

Tomas

Re: Help with building gstreamer-ti on beagleboard

[Robert P. J. Day]

On Tue, 13 Nov 2012, Tomas Frydrych wrote:

> On 13/11/12 15:22, Denys Dmytriyenko wrote:
> >> For Denzil it is not possible to arrange meta-yocto and meta-ti layers
> >> in a way that would work; this has been fixed in Danny (in
> >> meta-yocto-bsp). If you want to stick with Denzil, there are different
> >> ways to work around it, easiest should be to delete the offending
> >> beagleboard.conf from meta-yocto.
> >
> > Why can't you put meta-ti in front of meta-yocto in Denzil? Works just fine.
>
> Because meta-yocto layer.conf does:
>
>   BBPATH := "${LAYERDIR}:${BBPATH}"
>
> While meta-ti layer.conf does:
>
>   BBPATH .= ":${LAYERDIR}"
>
> So regardless how you order it, you get BBPATH that looks like:
>
>   meta-yocto:meta:meta-ti
>
> Which guarantees you the beagleboard.conf from meta-yocto.

  once upon a time, i pointed out on the yocto list the inconsistency
of how different layer.conf files set BBPATH:

https://lists.yoctoproject.org/pipermail/yocto/2012-March/007660.html

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: Help with building gstreamer-ti on beagleboard

[Denys Dmytriyenko]

On Tue, Nov 13, 2012 at 10:43:05AM -0500, Robert P. J. Day wrote:
> On Tue, 13 Nov 2012, Tomas Frydrych wrote:
> 
> > On 13/11/12 15:22, Denys Dmytriyenko wrote:
> > >> For Denzil it is not possible to arrange meta-yocto and meta-ti layers
> > >> in a way that would work; this has been fixed in Danny (in
> > >> meta-yocto-bsp). If you want to stick with Denzil, there are different
> > >> ways to work around it, easiest should be to delete the offending
> > >> beagleboard.conf from meta-yocto.
> > >
> > > Why can't you put meta-ti in front of meta-yocto in Denzil? Works just fine.
> >
> > Because meta-yocto layer.conf does:
> >
> >   BBPATH := "${LAYERDIR}:${BBPATH}"
> >
> > While meta-ti layer.conf does:
> >
> >   BBPATH .= ":${LAYERDIR}"
> >
> > So regardless how you order it, you get BBPATH that looks like:
> >
> >   meta-yocto:meta:meta-ti
> >
> > Which guarantees you the beagleboard.conf from meta-yocto.
> 
>   once upon a time, i pointed out on the yocto list the inconsistency
> of how different layer.conf files set BBPATH:

Yes, it was fixed already.

-- 
Denys

Re: Help with building gstreamer-ti on beagleboard

[Flavio Castro Alves Filho]

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

2012/11/13 Denys Dmytriyenko <denys@ti.com>

> On Tue, Nov 13, 2012 at 10:43:05AM -0500, Robert P. J. Day wrote:
> > On Tue, 13 Nov 2012, Tomas Frydrych wrote:
> >
> > > On 13/11/12 15:22, Denys Dmytriyenko wrote:
> > > >> For Denzil it is not possible to arrange meta-yocto and meta-ti
> layers
> > > >> in a way that would work; this has been fixed in Danny (in
> > > >> meta-yocto-bsp). If you want to stick with Denzil, there are
> different
> > > >> ways to work around it, easiest should be to delete the offending
> > > >> beagleboard.conf from meta-yocto.
> > > >
> > > > Why can't you put meta-ti in front of meta-yocto in Denzil? Works
> just fine.
>

I did that here and it doens't work.


> > >
> > > Because meta-yocto layer.conf does:
> > >
> > >   BBPATH := "${LAYERDIR}:${BBPATH}"
> > >
> > > While meta-ti layer.conf does:
> > >
> > >   BBPATH .= ":${LAYERDIR}"
> > >
> > > So regardless how you order it, you get BBPATH that looks like:
> > >
> > >   meta-yocto:meta:meta-ti
> > >
> > > Which guarantees you the beagleboard.conf from meta-yocto.
> >
> >   once upon a time, i pointed out on the yocto list the inconsistency
> > of how different layer.conf files set BBPATH:
>
> Yes, it was fixed already.
>
> --
> Denys
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>



-- 
Flavio de Castro Alves Filho

flavio.alves@gmail.com
www.linuxembarcado.com
Twitter: http://twitter.com/#!/fraviofii
LinkedIn profile: www.linkedin.com/in/flaviocastroalves

[-- Attachment #2: Type: text/html, Size: 2887 bytes --]

Re: Help with building gstreamer-ti on beagleboard

[Tomas Frydrych]

On 13/11/12 21:25, Flavio Castro Alves Filho wrote:
> 2012/11/13 Denys Dmytriyenko <denys@ti.com>
>>>>> Why can't you put meta-ti in front of meta-yocto in Denzil? Works
>> just fine.
> 
> I did that here and it doens't work.

As I explained earlier, for Denzil the order makes no real difference.
Just delete meta-yocto/conf/machine/beagleboard.conf.

But this has been all sorted out in the Danny release by splitting out
the bsp stuff into meta-yocto-bsp; if you are creating a new set up you
would be better to use Danny anyway.

Tomas

-- 
http://sleepfive.com

Re: Help with building gstreamer-ti on beagleboard

[Flavio Castro Alves Filho]

[-- Attachment #1: Type: text/plain, Size: 17694 bytes --]

2012/11/13 Tomas Frydrych <tf+lists.yocto@r-finger.com>

> On 13/11/12 21:25, Flavio Castro Alves Filho wrote:
> > 2012/11/13 Denys Dmytriyenko <denys@ti.com>
> >>>>> Why can't you put meta-ti in front of meta-yocto in Denzil? Works
> >> just fine.
> >
> > I did that here and it doens't work.
>
> As I explained earlier, for Denzil the order makes no real difference.
> Just delete meta-yocto/conf/machine/beagleboard.conf.
>

I did this and it worked.


>
> But this has been all sorted out in the Danny release by splitting out
> the bsp stuff into meta-yocto-bsp; if you are creating a new set up you
> would be better to use Danny anyway.
>
> Tomas
>
> --
> http://sleepfive.com
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>


Now I'm facing a compilation issue in ti-dsplink recipe. It's a compilation
issue.

Here it is the error message (sorry for the bad log. I had to use external
access using a putty on Windows this time).

/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal
>/dev/null
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_ringio.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/INCLUDE/USER/.
>/dev/null
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
"" "mkdir -p
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_ringio.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal
>/dev/null
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_mpcs.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/INCLUDE/USER/.
>/dev/null
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
"" "mkdir -p
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_mpcs.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal
>/dev/null
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_mpcs_os.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/INCLUDE/USER/.
>/dev/null
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
"" "mkdir -p
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_mpcs_os.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal
>/dev/null
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_mplist.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/INCLUDE/USER/.
>/dev/null
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
"" "mkdir -p
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_mplist.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal
>/dev/null
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_pool.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/INCLUDE/USER/.
>/dev/null
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
"" "mkdir -p
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_pool.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal
>/dev/null
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_notify.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/INCLUDE/USER/.
>/dev/null
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
"" "mkdir -p
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal"
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/_notify.h
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/export/INCLUDE/Linux/OMAP3530/internal
>/dev/null
| [API                 ] ------- OBJECT ---------------- DEBUG
--------------
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api"
"make -C
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api
-f
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/Linux/OMAP3530/
compile.mk objdeb VERBOSE=0" ""
| make[1]: Entering directory
`/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api'
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD"
""  "mkdir -p
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD"
| echo Fetching the configuration file CFG_OMAP3530_SHMEM.c ...
| Fetching the configuration file CFG_OMAP3530_SHMEM.c ...
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/all/CFG_OMAP3530_SHMEM.c
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD/.
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD"
""  "mkdir -p
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD"
| echo Fetching the configuration file CFG_Linux.c ...
| Fetching the configuration file CFG_Linux.c ...
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/all/CFG_Linux.c
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD/.
| /usr/bin/perl
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/make/bin/
runif.pl LINUX "exist
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD"
""  "mkdir -p
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD"
| echo Fetching the configuration file CFG_ARM.c ...
| Fetching the configuration file CFG_ARM.c ...
| cp
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/all/CFG_ARM.c
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD/.
| echo Compiling CFG_system.c...
| Compiling CFG_system.c...
| /arm-poky-linux-gnueabi-gcc -g -DOS_LINUX -DMAX_DSPS=1 -DMAX_PROCESSORS=2
-DID_GPP=1 -DOMAP3530 -DPROC_COMPONENT -DPOOL_COMPONENT -DNOTIFY_COMPONENT
-DMPCS_COMPONENT -DRINGIO_COMPONENT -DMPLIST_COMPONENT -DMSGQ_COMPONENT
-DMSGQ_ZCPY_LINK -DCHNL_COMPONENT -DCHNL_ZCPY_LINK -DZCPY_LINK
-DKFILE_DEFAULT -DOMAP3530 -DOMAP3530_PHYINTERFACE=SHMEM_INTERFACE
-DGPP_SWI_MODE
-I/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/inc
-I/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/inc/usr
-I/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/inc/sys/Linux
-I/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/inc/sys/Linux/2.6.18
-I/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api
-I/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/Linux
-I/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gERROR:
Function failed: do_compile (see
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/temp/log.do_compile.4141
for further information)
|
nueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api/Linux/2.6.18
-I/home/flavio/toolchains/git/arm-2009q1-203/arm-none-linux-gnueabi/libc/usr/include
-I/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/INCLUDE/USER
-I/home/flavio/toolchains/git/arm-2009q1-203/arm-none-linux-gnueabi/libc/usr/include
-Wall -c   -D_REENTRANT -DTRACE_USER -DDDSP_DEBUG
-DKBUILD_BASENAME=CFG_system
-o/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/API/OBJ/DEBUG/CFG_system.o
/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD/CFG_system.c
| make[1]: /arm-poky-linux-gnueabi-gcc: Command not found
| make[1]: ***
[/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/config/BUILD/CFG_system.c.deb]
Error 127
| make[1]: Leaving directory
`/home/prjs/tk0001/philinux/philinux-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/ti-dsplink-1_1_65_00_03-r121j/dsplink_linux_1_65_00_03/dsplink/gpp/src/api'
| make: *** [objdeb] Error 2
NOTE: package ti-dsplink-1_1_65_00_03-r121j: task do_compile: Failed
ERROR: Task 256 (/home/prjs/tk0001/philinux/meta-ti/recipes-ti/dsplink/
ti-dsplink_1.65.00.03.bb, do_compile) failed with exit code '1'
Waiting for 1 running tasks to finish:
0: ti-linuxutils-1_2_26_01_02-r121e do_make_scripts (pid 4142)
NOTE: package ti-linuxutils-1_2_26_01_02-r121e: task do_make_scripts:
Succeeded
NOTE: Tasks Summary: Attempted 670 tasks of which 668 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
  /home/prjs/tk0001/philinux/meta-ti/recipes-ti/dsplink/
ti-dsplink_1.65.00.03.bb, do_compile
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

I'm using Ubuntu 12.04 to build. Is it a problem? Should I need some
special configuration in my Ubuntu in order to have it working?

Best regards,

Flavio

-- 
Flavio de Castro Alves Filho

flavio.alves@gmail.com
www.linuxembarcado.com
Twitter: http://twitter.com/#!/fraviofii
LinkedIn profile: www.linkedin.com/in/flaviocastroalves

[-- Attachment #2: Type: text/html, Size: 19725 bytes --]

Re: Help with building gstreamer-ti on beagleboard

[Denys Dmytriyenko]

On Tue, Nov 13, 2012 at 03:38:25PM +0000, Tomas Frydrych wrote:
> On 13/11/12 15:22, Denys Dmytriyenko wrote:
> >> For Denzil it is not possible to arrange meta-yocto and meta-ti layers
> >> in a way that would work; this has been fixed in Danny (in
> >> meta-yocto-bsp). If you want to stick with Denzil, there are different
> >> ways to work around it, easiest should be to delete the offending
> >> beagleboard.conf from meta-yocto.
> > 
> > Why can't you put meta-ti in front of meta-yocto in Denzil? Works just fine.
> 
> Because meta-yocto layer.conf does:
> 
>   BBPATH := "${LAYERDIR}:${BBPATH}"
> 
> While meta-ti layer.conf does:
> 
>   BBPATH .= ":${LAYERDIR}"
> 
> So regardless how you order it, you get BBPATH that looks like:
> 
>   meta-yocto:meta:meta-ti
> 
> Which guarantees you the beagleboard.conf from meta-yocto.

Ah, right, that was part of the fix couple months ago in the master, besides 
splitting the meta-yocto-bsp off, which got into Danny, but not Denzil. I 
completely forgot about it... Thanks.

-- 
Denys

Re: Help with building gstreamer-ti on beagleboard

[Denys Dmytriyenko]

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

Re: Help with building gstreamer-ti on beagleboard

[Flavio Castro Alves Filho]

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

2012/11/13 Denys Dmytriyenko <denys@ti.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}"
>
>
Yes. I did that ant it worked. At least for this recipe.


> --
> Denys
>



-- 
Flavio de Castro Alves Filho

flavio.alves@gmail.com
www.linuxembarcado.com
Twitter: http://twitter.com/#!/fraviofii
LinkedIn profile: www.linkedin.com/in/flaviocastroalves

[-- Attachment #2: Type: text/html, Size: 2080 bytes --]

Re: Help with building gstreamer-ti on beagleboard

[Flavio Castro Alves Filho]

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

It worked.

I had a problem with a recipe at a fetch step, but it was an internet issue.

That's great!! Thank you very much.

Best regards,

Flavio


2012/11/14 Flavio Castro Alves Filho <flavio.alves@gmail.com>

>
>
>
> 2012/11/13 Denys Dmytriyenko <denys@ti.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}"
>>
>>
> Yes. I did that ant it worked. At least for this recipe.
>
>
>>  --
>> Denys
>>
>
>
>
> --
> Flavio de Castro Alves Filho
>
> flavio.alves@gmail.com
> www.linuxembarcado.com
> Twitter: http://twitter.com/#!/fraviofii
> LinkedIn profile: www.linkedin.com/in/flaviocastroalves
>
>


-- 
Flavio de Castro Alves Filho

flavio.alves@gmail.com
www.linuxembarcado.com
Twitter: http://twitter.com/#!/fraviofii
LinkedIn profile: www.linkedin.com/in/flaviocastroalves

[-- Attachment #2: Type: text/html, Size: 3260 bytes --]

Re: Help with building gstreamer-ti on beagleboard

[Flavio Castro Alves Filho]

[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]

I just would like to inform you that there is a detail regarding the build
od ti-dsplink recipe.

The directory structure must not have any '.' In the path. If it has, the
build will fail.

Best regards,

Flavio
 Em 14/11/2012 16:09, "Flavio Castro Alves Filho" <flavio.alves@gmail.com>
escreveu:

> It worked.
>
> I had a problem with a recipe at a fetch step, but it was an internet
> issue.
>
> That's great!! Thank you very much.
>
> Best regards,
>
> Flavio
>
>
> 2012/11/14 Flavio Castro Alves Filho <flavio.alves@gmail.com>
>
>>
>>
>>
>> 2012/11/13 Denys Dmytriyenko <denys@ti.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}"
>>>
>>>
>> Yes. I did that ant it worked. At least for this recipe.
>>
>>
>>>  --
>>> Denys
>>>
>>
>>
>>
>> --
>> Flavio de Castro Alves Filho
>>
>> flavio.alves@gmail.com
>> www.linuxembarcado.com
>> Twitter: http://twitter.com/#!/fraviofii
>> LinkedIn profile: www.linkedin.com/in/flaviocastroalves
>>
>>
>
>
> --
> Flavio de Castro Alves Filho
>
> flavio.alves@gmail.com
> www.linuxembarcado.com
> Twitter: http://twitter.com/#!/fraviofii
> LinkedIn profile: www.linkedin.com/in/flaviocastroalves
>
>

[-- Attachment #2: Type: text/html, Size: 3795 bytes --]