**** BEGIN LOGGING AT Tue Jul 22 03:00:01 2014 Jul 22 08:11:08 good morning Jul 22 08:35:36 morning all Jul 22 09:45:53 Hi yocto.. Jul 22 09:47:59 I am trying to compile mplayer but it's showing error as mentioned in the weblink how to rectify this. http://pastebin.com/HfPRDHwb Jul 22 09:51:58 embed: what version of metadata? Jul 22 09:53:04 x264 was moved from meta-oe to oe-core in dora, so I guess it's something rather old and download issues are kind of expected if you don't have good premirror **** BEGIN LOGGING AT Tue Jul 22 09:55:15 2014 Jul 22 09:58:55 JaMa: please check ths web link http://pastebin.com/XnE8Yq3a Jul 22 10:00:09 embed: you need something like http://bpaste.net/show/487545/ Jul 22 10:01:01 if you don't want to change version you need to find corresponding SRCREV to what was used in dylan Jul 22 11:32:35 Hi everybody Jul 22 11:36:26 I've got a short question concerning patches; I've added a patch to a recipe that worked before, and now it fails with the error "can't find file to patch". Patch depth is 1, which is the default as I got from the documentation. I've got no idea what's wrong here. Anybody able to help me? Jul 22 11:36:51 Is there a certain format that patches have to have? I created my patch with "diff -Nurp" Jul 22 11:37:13 Hi while compiling mplayer i am getting pastebin error hoe to rectify this error. http://pastebin.com/6r4L0KY7 Jul 22 11:38:19 hi, is there any way to add application to an image that already built with yocto? I mean I want to install new app. in my built image... Jul 22 11:38:40 embed: Do you have libav installed? Errors seem to be related: "Checking for Libav (libavutil > 51.21.0:libavcodec >= 54.25.0:libavformat > 53.20.0:libswscale >= 2.0.0:libavresample >= 1.0.0) ... | Error: Unable to find development files for some of the required Libav libraries above. Aborting." Jul 22 11:39:16 before compiling mplayer libav has compiled.. Jul 22 11:39:17 sm_: Is there already a recipe for your package? Jul 22 11:39:36 embed: which libav version 8 or 9? Jul 22 11:39:47 mplayer2 in meta-oe depends on libav-9 now Jul 22 11:40:00 I don't know about meta-beagleboard/common-bsp/recipes-sdk/mplayer/mplayer2_git.bb Jul 22 11:41:40 actually I want to know both cases, with & without recipe... Jul 22 11:42:03 lackS: actually I want to know both cases, with & without recipe... Jul 22 11:42:32 libav version is libav-0.8.4+gitAUTOINC+2c8ce46250ff78191fe6565876ddc4bc03fdf519-r8.0 do_package_setscene Jul 22 11:42:59 sm_: With recipe, it's easy: Add the name of the package to IMAGE_INSTALL variable located in the recipe for your image Jul 22 11:43:07 e.g. IMAGE_INSTALL += "vim" Jul 22 11:43:33 You could also create an xy-extra.inc file, which holds your customizations, and include this into the recipe of your image Jul 22 11:44:42 I'm having issues building a custom package Jul 22 11:44:53 is there a way I can run bitbake and get a sort for chroot Jul 22 11:44:58 lackS: I know IMAGE_INSTALL variable, I mean after building an image and its fileSystem... not before Its building. Jul 22 11:45:04 where I can try to run the build steps manually and debug? Jul 22 11:45:18 sort of* Jul 22 11:45:25 tmpsantos, bitbake -c devshell Jul 22 11:46:04 kroon: \o/ perfect Jul 22 11:46:09 thanks Jul 22 11:49:09 sm_: You can simply execute bitbake -k again and it will build a new image -- but only if you still own the working tree. Jul 22 11:52:26 lackS: I mean modify built image! I don't want to build new image. Jul 22 11:53:28 This will be the very same image as it was before, plus your added package. BitBake does not recreate everything on every run. Indeed, the -k option tells BitBake to continue as much as possible instead of re-doing things. Jul 22 11:55:39 i khow but by this way thw new image will be built Jul 22 11:56:46 lackS: i mean is i possible to modify existing image and dont build new image that is located in /tmp/deploy/images directory Jul 22 11:57:09 lackS: i khow but by this way thw new image will be built Jul 22 12:04:02 sm_: I'm sorry, I don't know whether this is possible :-/ Jul 22 12:06:22 lackS: no prob. thanks. let me ask you another question if U know. do you know is the file-system of an built image read-only or not? Jul 22 12:11:39 Hi yocto..I enabled camera in kernel and /dev/video0 detected but am struggling with interfacing the camera. Jul 22 12:12:21 i enabled v4l2-utils.. Jul 22 12:13:02 any one can help how to access v4l2 commands.. Jul 22 12:28:53 please any one can help me to shot out this issue. Jul 22 12:35:32 sm_: Sorry, can't really answer that either. I bet it's a question of configuration. Jul 22 14:27:11 Hi, with latest poky , I am getting this error in core-image-minimal for qemumips : /etc/rcS.d/S55bootmisc.sh: line 73: syntax error: bad substitution ( caused by commit id: 00017b4dd895afff9ff613d511cea373f13a96ea) Jul 22 14:33:34 maxin: file a bug please Jul 22 14:33:48 rburton: ok. Jul 22 14:37:06 rburton, you have any comments on the gdkpixbuf issue I had ? I could leave it for now, still it would be nice to get this sorted out Jul 22 14:39:18 seems sth. pulled from last week triggers this in a variant I have of build-appliance: Jul 22 14:39:22 ERROR: QA Issue: serf: Files/directories were installed but not shipped Jul 22 14:39:33 anyone seen that before I investigate further? Jul 22 14:41:43 kroon: will be pondering that shortly Jul 22 14:56:06 rburton, great Jul 22 17:23:38 I set the following in a .bbappend file Jul 22 17:23:50 PF="${PN}-${EXTENDPE}${PV}-${PR}-cv${PERFORCE_CHANGELIST}" Jul 22 17:24:05 somehow, it never makes it into the packagefile Jul 22 17:25:12 what am I missing? Jul 22 17:25:53 volker-: what are you trying to do? Jul 22 17:26:42 bluelightning: adjusting the package name of all files that are modified via bbappend Jul 22 17:27:22 bluelightning: PV="${PV}-cvXXXX" doesn't work because it is reusing the PV variable in itself Jul 22 17:28:00 volker-: I don't think PF is used in the way you think it is Jul 22 17:28:13 did you perhaps try PV_append = ? Jul 22 17:31:30 bbl Jul 22 17:31:30 nope, didn't try PV_append, didn't thought about it. Jul 22 17:31:40 you may find that does what you want Jul 22 17:31:46 but the ref-manual states about PF " Specifies the recipe or package name and includes all version and revision numbers" Jul 22 17:32:26 P/PF are variables that reference PN/PV/PR/PE, for convenience only. plenty of spots in the metadata use PN/PV/PE/PR directly Jul 22 17:32:35 so overriding the former wouldn't have any effect on the latter Jul 22 17:32:43 override the components, not the vars that happen to reference them Jul 22 17:33:00 ok. My understanding was to use it in the recipe Jul 22 17:33:13 will will try the PV_append later. First lunch, brb. Jul 22 17:34:55 I'd suggest reading some recipes and appends Jul 22 17:35:00 no one ever modifies P/PF :) Jul 22 18:03:13 RP, heads up - found a QA issue/error in your recently added serf recipe -- bug 6567 Jul 22 18:03:14 Bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=6567 normal, Undecided, ---, saul.wold, NEW , recent addition of serf recipe causes QA issues and do_rootfs failure Jul 22 18:06:22 one could argue that build-appliance doesn't need subversion ; my builders that are ubuntu based don't have it installed. Jul 22 18:07:00 (as serf was added for subversion) Jul 22 18:07:14 * paulg makes such an exclusion locally Jul 22 18:10:33 Hmm, is PACKAGE_EXCLUDE not supported by OpkgPM? Doesn't seem so Jul 22 18:24:38 PV_append does not work too great if you use PV when downloading the file (like ntp does) Jul 22 18:26:03 errr. my fault, should have used PR append, now it seems to work, mixed it up with PV. Jul 22 18:26:16 if all you want is to alter packaging, you can alter the packaging variables, also Jul 22 18:26:24 PKGV/PKGR, which default to PV/PR Jul 22 18:27:19 kergoth: from my understanding they drop then the PR naming in the file Jul 22 18:27:40 PR is generally dealt with automatically based on metadata changes now, yes Jul 22 18:28:09 I think PR_append does the trick, just mistyped with with PV Jul 22 20:27:43 hello all Jul 22 20:29:24 is it correct assumption that if I want to implement a new image type via IMAGE_CMD_foo , which is also compressed and which depends on previously generated ext4 root filesystem, I need to use IMAGE_TYPEDEP_foo = "ext4" and IMAGE_TYPEDEP_foo.bz2 = "foo" ? Jul 22 20:29:43 or is the compression part handled somehow differently ? Jul 22 20:29:53 Hello. How do I make bitbake treat QA issues as warnings for my layer? I tried adding WARN_QA += "my-recipe" to local.conf but no luck. Jul 22 20:31:40 kspr: INSANE_SKIP Jul 22 20:35:21 JaMa, thank you very much. Do I need to do it in all recipes which has QA issues (installed but not shipped), or can I do it globaly? Jul 22 20:35:47 kspr: it would be much better to fix it in the recipes Jul 22 20:36:18 you can remove it from WARN_QA globally Jul 22 20:36:33 JaMa, I know, and will do, but I'm a bit in a hurry.. it is a lot of Perl recipes which is .. insane. Jul 22 20:36:47 something like WARN_QA_remove = "installed-vs-shipped" Jul 22 20:37:43 Alright, thank you very much :) Jul 22 22:37:48 pidge, I'm here. Also at OSCON if you are. Jul 22 22:40:57 halstead: nah, I'm at home today working. I'll be down there all day tomorrow and the next (had to do the libreoffice doesn't convert correctly to pptx shuffle today) Jul 22 23:33:07 halstead: what's oscon like? I've never been. Jul 22 23:34:38 darknighte: it's fun. Chatting with friends and vendors. **** ENDING LOGGING AT Wed Jul 23 03:00:01 2014