[yocto] Can't override task from bbclass with - in its name
I have custom classes that override a task thus (in foo.bbclass)
foo_do_something () {
...
}
EXPORT_FUNCTIONS do_something
but if I change the name to foo-bar.bbclass and change the class thus
foo-bar_do_something () {
...
}
EXPORT_FUNCTIONS do_something
then building fails with "foo-bar_do_something: not found" and, sure enough,
run.do_something does not contain the definition of foo-bar_do_something.
Is this a known issue?
MV
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Can't override task from bbclass with - in its name
On Sun, Oct 26, 2014 at 8:15 AM, Vuille, Martin (Martin)
wrote:
> I have custom classes that override a task thus (in foo.bbclass)
>
> foo_do_something () {
> ...
> }
>
> EXPORT_FUNCTIONS do_something
>
> but if I change the name to foo-bar.bbclass and change the class thus
>
> foo-bar_do_something () {
> ...
> }
>
> EXPORT_FUNCTIONS do_something
>
> then building fails with "foo-bar_do_something: not found" and, sure
> enough,
> run.do_something does not contain the definition of foo-bar_do_something.
>
- isn't a valid character in a shell function, so while potentially
irritating, it's not surprising :)
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Can't override task from bbclass with - in its name
> From: kerg...@gmail.com [mailto:kerg...@gmail.com] On Behalf Of Christopher > Larson > > - isn't a valid character in a shell function, so while potentially > irritating, it's not surprising :) Hmm, good point! Thanks MV -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] "File exists" exception when IMAGE_LINK_NAME is empty ("")
On 25 October 2014 22:12, Vuille, Martin (Martin) wrote: > Personally, I feel the correct behavior would be to not create the > symlinks when IMAGE_LINK_NAME is the empty string. > Seems reasonable, can you send a patch? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] bash tab completion not working
Hi all, I built image core-image-full-cmdline on a beaglebone black and the tab completion feature of bash is not working. Pressing the tab key just puts the cursor to the next tab stop. Looking at the bash binary on my workstation with the ldd command, I see it is dependent on libreadline, but I don't see that dependency on the binary of the beaglebone. I created a layer with a bash_4.3.bbappend file containing this: DEPENDS ?= "" DEPENDS += "ncurses readline" EXTRA_OECONF ?= "" EXTRA_OECONF += "--enable-readline --with-curses" I also added the layer to the build/conf/bblayers.conf file. Alas, after rebuilding bash it still doesn't have a dependency on readline and tab completion still doesn't work. Would someone have a suggestion? -- D. Laroche -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bash tab completion not working
On 26 October 2014 21:41, Denis Laroche wrote: > I also added the layer to the build/conf/bblayers.conf file. Alas, > after rebuilding bash it still doesn't have a dependency on readline > and tab completion still doesn't work. > > Would someone have a suggestion? > Did you check the configure log to verify that bash was actually enabling readline, and if not then it hopefully says why. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bash tab completion not working
2014-10-26 17:59 GMT-04:00 Burton, Ross : > > On 26 October 2014 21:41, Denis Laroche wrote: >> >> I also added the layer to the build/conf/bblayers.conf file. Alas, >> after rebuilding bash it still doesn't have a dependency on readline >> and tab completion still doesn't work. >> >> Would someone have a suggestion? > > > Did you check the configure log to verify that bash was actually enabling > readline, and if not then it hopefully says why. > > Ross Thanks for the reply. Yes I see the log of configure that readline is enabled: config.status: creating lib/readline/Makefile What's interesting is the binary I built is much bigger than the original (2963751 vs 847044 bytes). Looking at the log of the compile, I can see that readline is built and is linked statically, which would explain the bigger size of the executable and why ldd doesn't report it. But the end result is still the same. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Package not found in base feeds with custom BSP but default settings
Hi All, I have not so much experience with oe, and I am facing an error that I cannot understand yet. I tried to search on the web about his issue, but I did not find any useful result. Here is what I did with my oe : - Install yocto project and checkout daisy branch - Set up a build directory : myBeagle - Configure for beaglebone - bitbake core-image-minimal => Everything is OK Now I wan to create my own BSP - Setup a BSP layer with the yocto-bsp create tool => meta-myBeagleBSP - Config is let by default for beaglebone - Update my local.conf to select myBeagleBSP target - bitbake core-image-minimal => Everything seems to build fine => But when running the do_rootfs, I get this error message : ERROR: packagegroup-core-boot not found in the base feeds (myBeagleBSP armv7a-vfp-neon armv7a-vfp armv7a armv6-vfp armv6 armv5e-vfp armv5e armv5-vfp armv5 armv4 arm noarch any all) This is followed by tons of package names in red. I found in the document that the base feeds is the content of the folders under tmp/deploy/rpm and in the tmp/deploy/rpm/myBeagleBSP folder I can find these packages : packagegroup-core-boot-1.0-r17.mybeaglebsp.rpm packagegroup-core-boot-dbg-1.0-r17.mybeaglebsp.rpm packagegroup-core-boot-dev-1.0-r17.mybeaglebsp.rpm So I think that I am missing something, but I don't know what . I let nearly every settings to default values. And I cannot figure out why the beaglebone machine can build fine but my own machine with same settings is failing... Thanks, best regards ~Slyde~ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Package Report System]Manual check recipes name list
This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can check the detail information at http://packages.yoctoproject.org/manuallychkinfo PackageName Version LastChkVersion LastChkTime Maintainer NoUpgradeReason man 1.6gN/A 41937 d Saul Wold -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Package Report System]Upgrade recipes name list
This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 because the new version is unstable" You can check the detail information at http://packages.yoctoproject.org/upgradepkgname PackageName Version UpVersion MaintainerNoUpgradeReason ccache3.1.9 3.1.10 Wenzong Fan chkconfig 1.3.581.3.62 Wenzong Fan gettext 0.18.3.2 0.19.3 Wenzong Fan blktrace 1.0.5+gitAUTOINC+d6918c8 1.1.0+gitAUTOINC+2cf87e6 Tom Zanussi systemtap-uprobes 2.5+gitAUTOINC+8f0fcd995f 2.6+gitAUTOINC+dc7bb40Tom Zanussi sysprof 1.2.0+gitAUTOINC+cd44ee6 1.2.0+gitAUTOINC+6901897 Tom Zanussi npth 0.91 1.0 Saul Wold lsbinitscripts9.55 9.56.1 Saul Wold apt 0.9.9.4 1.0.9.3 Saul Wold mc4.8.124.8.13 Saul Wold mkelfimage4.0+gitAUTOINC+686a48a339 4.0+gitAUTOINC+dc878b4Saul Wold mtd-utils 1.5.1+gitAUTOINC+9f10713 1.5.1+gitAUTOINC+dd183c2 Saul Wold u-boot-mkimagev2013.07+gitAUTOINC+62c1 v2013.07+gitAUTOINC+5b3e Saul Wold cups 1.7.5 2.0.0 Saul Wold hdparm9.43 9.45 Saul Wold dpkg 1.17.41.17.21 Saul Wold libaio0.3.109 0.3.110 Saul Wold kmod 18+gitAUTOINC+ae58de0fcb 18+gitAUTOINC+9b34db1 Saul Wold help2man-native 1.46.11.46.4 Saul Wold systemtap 2.5+gitAUTOINC+8f0fcd995f 2.6+gitAUTOINC+dc7bb40Saul Wold libgcrypt 1.6.1 1.6.2 Saul Wold libxkbcommon 0.4.3 0.5.0 Saul Wold valgrind 3.9.0 3.10.0 Saul Wold resolvconf1.75 1.76 Saul Wold sqlite3 3.8.6.0 3080700 Saul Wold libunique 1.1.6 3.0.2 Saul WoldDo not upgrade to version: 2 liburcu 0.8.4 0.8.5 Saul Wold less 466 470 Saul Wold babeltrace1.2.1+gitAUTOINC+66c2a20 1.2.3+gitAUTOINC+074ee56 Saul Wold man-pages 3.71 3.75 Saul Wold mx-1.01.4.7+gitAUTOINC+9b1db6b 1.99.4+gitAUTOINC+63da1f2 Saul Wold PRS 1.99 is dev version watchdog 5.13 5.14 Saul Wold cronie1.4.111.4.12 Saul Wold usbutils 007 008 Saul Wold at3.1.153.1.16 Saul Wold curl
[yocto] Release Candidate Build for yocto-1.6.2.rc1 now available.
-e A release candidate build for yocto-1.6.2.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.6.2.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : d9eaf5edeb848671db0a7ac864850833af82bef2 meta-fsl-arm : 4e694e727aa8babfd0ba06c5e98bab3753b39a8b meta-minnow : 58fd55eb321a875d4e51c5c430de4d725ec9ba4c meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 meta-fsl-ppc : 299f84cceccacd84651c1cefc1c34e66fb598a96 poky : 313864bf528696a72c3ee6b3dec1a0c7b0b223f6 This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Luajit Compile Error
Hi, I also build the package luajit ,but it has the following errors. Can someone help me? Thanks. --- [lixin@ubinux-yocto-15 temp]$ cat log.do_compile.14752 DEBUG: Executing shell function do_compile NOTE: make -j 10 CROSS=i586-poky-linux- TARGET_CFLAGS= --sysroot=/yocto/work001/fnst/lixin/poky/build.x86/tmp/sysroots/qemux86 -m32 -march=i586 TARGET_LDFLAGS= --sysroot=/yocto/work001/fnst/lixin/poky/build.x86/tmp/sysroots/qemux86 TARGET_SHLDFLAGS= --sysroot=/yocto/work001/fnst/lixin/poky/build.x86/tmp/sysroots/qemux86 HOST_CC=gcc -m32 Building LuaJIT 2.0.3 make -C src make[1]: Entering directory `/yocto/work001/fnst/lixin/poky/build.x86/tmp/work/i586-poky-linux/luajit/2.0.3-r0/LuaJIT-2.0.3/src' BUILDVM lj_vm.s BUILDVM lj_ffdef.h BUILDVM lj_bcdef.h Error: pointer size mismatch in cross-build. Try: make HOST_CC="gcc -m32" CROSS=... make[1]: *** [lj_vm.s] Error 1 Error: pointer size mismatch in cross-build. Try: make HOST_CC="gcc -m32" CROSS=... make[1]: *** Waiting for unfinished jobs make[1]: *** [lj_ffdef.h] Error 1 Error: pointer size mismatch in cross-build. Try: make HOST_CC="gcc -m32" CROSS=... make[1]: *** [lj_bcdef.h] Error 1 make[1]: Leaving directory `/yocto/work001/fnst/lixin/poky/build.x86/tmp/work/i586-poky-linux/luajit/2.0.3-r0/LuaJIT-2.0.3/src' make: *** [default] Error 2 ERROR: oe_runmake failed WARNING: /yocto/work001/fnst/lixin/poky/build.x86/tmp/work/i586-poky-linux/luajit/2.0.3-r0/temp/run.do_compile.14752:1 exit 1 from exit 1 ERROR: Function failed: do_compile (log file is located at /yocto/work001/fnst/lixin/poky/build.x86/tmp/work/i586-poky-linux/luajit/2.0.3-r0/temp/log.do_compile.14752) [lixin@ubinux-yocto-15 temp]$ -- > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] > On Behalf Of Albert K > Sent: Monday, September 29, 2014 1:34 PM > To: Khem Raj > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Luajit Compile Error > > Dear Sir, > > Thanks a million. Adding the gcc-multilib to the build host did the > trick. Works like a charm. Thanks again. > > On Mon, Sep 29, 2014 at 12:57 PM, Khem Raj wrote: > > On Sun, Sep 28, 2014 at 7:22 PM, Albert K wrote: > >> Dear all, > >> > >> I am getting error when i include luajit package from the > >> meta-embedded and this is build from the core-image-minimal > >> layer(yocto daisy). Can someone help to point me the right direction > >> for fixing the compile error as show below? Thanks. > >> > > > > its expecting 32bit gcc to be available on your build host. So install > > gcc-multilib on build machine and it should go on. > > > >> > >> yocto@ubuntu-yocto:/yocto/poky/build/tmp/work/i586-poky-linux/luajit/ > >> 2.0.2-r0/temp$ > >> cat log.do_compile.16806 > >> DEBUG: Executing shell function do_compile > >> NOTE: make -j 4 CROSS=i586-poky-linux- TARGET_CFLAGS= > >> --sysroot=/yocto/poky/build/tmp/sysroots/qemux86 TARGET_LDFLAGS= > >> --sysroot=/yocto/poky/build/tmp/sysroots/qemux86 TARGET_SHLDFLAGS= > >> --sysroot=/yocto/poky/build/tmp/sysroots/qemux86 HOST_CC=gcc -m32 > >> Building LuaJIT 2.0.2 make -C src > >> make[1]: Entering directory > >> `/yocto/poky/build/tmp/work/i586-poky-linux/luajit/2.0.2-r0/LuaJIT-2.0.2/src' > >> HOSTCChost/minilua.o > >> HOSTCChost/buildvm_asm.o > >> HOSTCChost/buildvm_peobj.o > >> HOSTCChost/buildvm_lib.o > >> In file included from host/buildvm_peobj.c:9:0: > >> host/buildvm.h:9:23: fatal error: sys/types.h: No such file or > >> directory #include > >>^ > >> In file included from host/buildvm_asm.c:6:0: > >> host/buildvm.h:9:23: fatal error: sys/types.h: No such file or > >> directory #include > >>^ > >> compilation terminated. > >> In file included from host/buildvm_lib.c:6:0: > >> host/buildvm.h:9:23: fatal error: sys/types.h: No such file or > >> directory #include > >>^ > >> compilation terminated. > >> compilation terminated. > >> make[1]: *** [host/buildvm_asm.o] Error 1 > >> make[1]: *** Waiting for unfinished jobs > >> make[1]: *** [host/buildvm_peobj.o] Error 1 > >> make[1]: *** [host/buildvm_lib.o] Error 1 In file included from > >> /usr/include/limits.h:25:0, > >> from > >> /usr/lib/gcc/x86_64-linux-gnu/4.8/include-fixed/limits.h:168, > >> from > >> /usr/lib/gcc/x86_64-linux-gnu/4.8/include-fixed/syslimits.h:7, > >> from > >> /usr/lib/gcc/x86_64-linux-gnu/4.8/include-fixed/limits.h:34, > >> from host/minilua.c:32: > >> /usr/include/features.h:374:25: fatal error: sys/cdefs.h: No such > >> file or directory # include > >> ^ > >> compilation terminated. > >> make[1]: *** [host/minilua.o] Error 1 > >> make[1]: Leaving directory > >> `/yocto/
