* ExpansionError during parsing
@ 2012-07-09 19:39 Ali Sayed
2012-07-31 20:08 ` Denys Dmytriyenko
0 siblings, 1 reply; 6+ messages in thread
From: Ali Sayed @ 2012-07-09 19:39 UTC (permalink / raw)
To: meta-ti
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
ERROR: ExpansionError during parsing /yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530_4.00.00.00.bb: Failure expanding variable FILESPATH, expression was ${@base_set_filespath([ "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530-4_00_00_00-${MACHINE_KERNEL_PR}a", "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530-4_00_00_00", "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530", "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530-4_00_00_00", "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530", "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/files", "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine" ], d)} which triggered exception SyntaxError: EOL while scanning string literal (FILESPATH, line 1)
I have this error when I tried to build an Angstrom image for beagle board.
I tried to add this line
BBMASK = ".*/meta-ti/recipes-misc/"
to conf/local.conf file , but the error still there.
also I saw this : https://lists.yoctoproject.org/pipermail/meta-ti/2012-June/001279.html
but my linux.inc is already hasn't require linux-tools.inc
[-- Attachment #2: Type: text/html, Size: 2470 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ExpansionError during parsing
2012-07-09 19:39 ExpansionError during parsing Ali Sayed
@ 2012-07-31 20:08 ` Denys Dmytriyenko
0 siblings, 0 replies; 6+ messages in thread
From: Denys Dmytriyenko @ 2012-07-31 20:08 UTC (permalink / raw)
To: Ali Sayed; +Cc: meta-ti
On Mon, Jul 09, 2012 at 12:39:18PM -0700, Ali Sayed wrote:
> ERROR: ExpansionError during parsing
> /yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530_4.00.00.00.bb:
> Failure expanding variable FILESPATH, expression was ${@base_set_filespath([
> "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530-4_00_00_00-${MACHINE_KERNEL_PR}a",
> "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530-4_00_00_00",
> "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530",
> "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530-4_00_00_00",
> "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/ti-codecs-omap3530",
> "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine/files",
> "/yocto/boards/beagle/poky/meta-ti/recipes-ti/codec-engine" ], d)} which
> triggered exception SyntaxError: EOL while scanning string literal
> (FILESPATH, line 1)
>
> I have this error when I tried to build an Angstrom image for beagle board.
Hmm, I don't think the above is the correct Angstrom configuration. Looks more
like the Poky one...
Can you show us your bblayers.conf?
> I tried to add this line
> BBMASK = ".*/meta-ti/recipes-misc/"
> to conf/local.conf file , but the error still there.
> also I saw this :https://lists.yoctoproject.org/pipermail/meta-ti/2012-June/001279.html
> but my linux.inc is already hasn't require linux-tools.inc
--
Denys
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ExpansionError during parsing
2014-09-09 15:19 ` Nemicolopterus Crypticus
@ 2014-09-09 15:22 ` Burton, Ross
0 siblings, 0 replies; 6+ messages in thread
From: Burton, Ross @ 2014-09-09 15:22 UTC (permalink / raw)
To: Nemicolopterus Crypticus; +Cc: yocto
On 9 September 2014 16:19, Nemicolopterus Crypticus
<ncrypticus@gmail.com> wrote:
> Ah I see - that makes sense, thank you.
>
> I found this:
> http://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#functions
>
> But I'm not sure how to tell whether a given do_<task> function is a shell
> function or a python function. Is there a way to find that out?
If you want to append/prepend then you'll need to look at the initial
definition - most of the core tasks are in base.bbclass or
package.bbclass.
Ross
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ExpansionError during parsing
2014-09-09 9:43 ` Burton, Ross
@ 2014-09-09 15:19 ` Nemicolopterus Crypticus
2014-09-09 15:22 ` Burton, Ross
0 siblings, 1 reply; 6+ messages in thread
From: Nemicolopterus Crypticus @ 2014-09-09 15:19 UTC (permalink / raw)
To: Burton, Ross; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
Ah I see - that makes sense, thank you.
I found this:
http://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#functions
But I'm not sure how to tell whether a given do_<task> function is a shell
function or a python function. Is there a way to find that out?
Also thanks for the hint about S or B - those may indeed be helpful!
On Tue, Sep 9, 2014 at 2:43 AM, Burton, Ross <ross.burton@intel.com> wrote:
> On 9 September 2014 01:22, Nemicolopterus Crypticus
> <ncrypticus@gmail.com> wrote:
> > do_install_prepend(){
> > bb.build.exec_func('do_change_dir', d)
> > }
> >
> > do_change_dir(){
> > cd <a directory>
> > }
>
> do_install is a shell function, so bitbake is parsing your python code as
> shell.
>
> You want to do this:
>
> do_install_prepend() {
> cd <somewhere>
> }
>
> If you need to do this though, have a look to see if setting S or B is
> sufficient.
>
> Ross
>
[-- Attachment #2: Type: text/html, Size: 1651 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ExpansionError during parsing
2014-09-09 0:22 Nemicolopterus Crypticus
@ 2014-09-09 9:43 ` Burton, Ross
2014-09-09 15:19 ` Nemicolopterus Crypticus
0 siblings, 1 reply; 6+ messages in thread
From: Burton, Ross @ 2014-09-09 9:43 UTC (permalink / raw)
To: Nemicolopterus Crypticus; +Cc: yocto
On 9 September 2014 01:22, Nemicolopterus Crypticus
<ncrypticus@gmail.com> wrote:
> do_install_prepend(){
> bb.build.exec_func('do_change_dir', d)
> }
>
> do_change_dir(){
> cd <a directory>
> }
do_install is a shell function, so bitbake is parsing your python code as shell.
You want to do this:
do_install_prepend() {
cd <somewhere>
}
If you need to do this though, have a look to see if setting S or B is
sufficient.
Ross
^ permalink raw reply [flat|nested] 6+ messages in thread
* ExpansionError during parsing
@ 2014-09-09 0:22 Nemicolopterus Crypticus
2014-09-09 9:43 ` Burton, Ross
0 siblings, 1 reply; 6+ messages in thread
From: Nemicolopterus Crypticus @ 2014-09-09 0:22 UTC (permalink / raw)
To: yocto
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
I can't seem to get simple bash code to parse properly in my recipes.
I have something like this:
do_install_prepend(){
bb.build.exec_func('do_change_dir', d)
}
do_change_dir(){
cd <a directory>
}
I get this when I try bitbake -c clean -f <project>:
NOTE: Error during finalise of <path>/<to>/<recipe>/recipe.bb |
ETA: --:--:--
ERROR: ExpansionError during parsing <path>/<to>/<recipe>/recipe.bb:
Failure expanding variable do_install: ShellSyntaxError:
LexToken(TOKEN,"'do_change_dir',",0,0)
followed by:
LexToken(TOKEN,'d',0,0)
LexToken(RPARENS,')',0,0)
LexToken(NEWLINE,'\n',0,0)
LexToken(TOKEN,'autotools_do_install',0,0)
LexToken(NEWLINE,'\n',0,0)
This looks identical to this:
https://www.mail-archive.com/yocto%40yoctoproject.org/msg09403.html
https://www.mail-archive.com/yocto%40yoctoproject.org/msg04862.html
What am I missing?
[-- Attachment #2: Type: text/html, Size: 1567 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-09-09 15:23 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-09 19:39 ExpansionError during parsing Ali Sayed
2012-07-31 20:08 ` Denys Dmytriyenko
2014-09-09 0:22 Nemicolopterus Crypticus
2014-09-09 9:43 ` Burton, Ross
2014-09-09 15:19 ` Nemicolopterus Crypticus
2014-09-09 15:22 ` Burton, Ross
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.