**** BEGIN LOGGING AT Fri Jul 07 03:00:03 2017 Jul 07 06:17:56 How can I add or modify the yocto screensaver ? Jul 07 07:44:02 RP: I'm currently struggling to understand why do_rootfs gets executed again. 1.0-r0.do_rootfs.d9e41ef4370dd370ddd2cf647f734468 under "stamps" is the same each time, it just gets created anew/ Jul 07 07:44:20 So it is not a task signature change which triggers the re-execution. Jul 07 07:44:27 What else is bitbake looking at? Jul 07 07:45:45 In addition to do_rootfs, do_prepare_recipe_sysroot also runs again. Jul 07 07:45:57 But like do_rootfs, there's no signature change for it. Jul 07 07:47:15 I'm not seeing this when just calling "bitbake :do_rootfs". Could it be that some of the additional tasks "invalidate" the sysroot and/or rootfs? Jul 07 07:50:03 It is the "stamps" directory which records which tasks were already executed, right? Jul 07 07:54:01 Hmm, do_image modifies the rootfs (for example, by creating /etc/build, which includes the BUILD_ID). But can that influence whether the do_rootfs task gets run again? Probably not. Jul 07 08:03:59 RP: to make it even worse, I can't reproduce it with plain "bitbake", only when invoked via oe-selftest. Jul 07 08:15:59 pohly: You're right that stamps should control this and it shouldn't rerun if its run once unless the config changes Jul 07 08:16:30 RP: any suggestion for how I can debug this further? Jul 07 08:19:51 pohly: this happens even with the single oe-selftest? Jul 07 08:20:47 RP: just a single selftest runs. It creates the .bb, adds it to BBFILES, and calls bitbake. Jul 07 08:20:50 joshuagl: still SDL issues on opensuse423 https://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/1135 :( Jul 07 08:21:11 But the .bb file always has the same content, so except for re-parsing I'd not expect anything to change. Jul 07 08:21:45 I'm currently experimenting with a version of the selftest that uses a "normal" .bb in the layer. Jul 07 08:21:50 pohly: If the stamp sigs file is the same I'm equally puzzled :/ Jul 07 08:22:12 Somehow "dynamically create .bb" does have an effect :-/ Jul 07 08:23:24 It works as expected when using a fixed recipe a la meta-selftest. Jul 07 08:24:15 I was hoping to avoid creating such a layer for meta-refkit-core testing, thus the attempt to create additional recipes inside the test itself. Jul 07 08:24:53 RP: I can probably create a simple selftest that exhibits this in Poky. Do you think you can have a look when I file that as a bug? Jul 07 08:25:10 pohly: All I can say is that in theory I think it should work... Jul 07 08:28:52 RP: ack Jul 07 08:38:21 for some reason opensuse423 is running VNC on display 3, IIRC we expect display 1 ? Jul 07 08:41:08 joshuagl: I believe we do, yes Jul 07 09:28:03 Hi, What is the bes method to integrate a project with cascading Makefiles overriding CFLAGS and other variables. I'm lost with EXTRA_CFLAGS , EXTRA_OEMAKE, CFLAGS variables during the compile process. Jul 07 09:29:50 any link would be welcomed ! Jul 07 09:30:47 Hi guys, could someone explain what exactly means "not found in the feeds" message during do_rootfs? From where comes up the question: I'm currently install dev-pkgs into my image, but I have some -dev packages which are empty, so the "pkg-dev not found in the feeds" message during do_rootfs. My starting point was to add ALLOW_EMPTY_${PN}-dev = "1" to those package's recipes, but nothing changed. Jul 07 09:31:59 zero_note: ALLOW_EMPTY_${PN}-dev is already set to 1 by default Jul 07 09:32:06 hence why it didn't do anything Jul 07 09:33:05 basically this situation comes up when a recipe claims it will provide a package and then doesn't Jul 07 09:33:21 is the error actually about a -dev package or something else? Jul 07 09:33:59 bluelightning: actually about a -dev package and 2 -dbg others Jul 07 09:36:21 zero_note: do those packages exist under tmp/deploy/ipk ? Jul 07 09:40:07 adding more details: the -dev package simply fetch a tar.gz from git , unpack it and install the extracted files Jul 07 09:40:43 bluelightning: I have no tmp/deply/ipk directory Jul 07 09:41:31 zero_note: hold on a sec - do you have a recipe named something-dev ? Jul 07 09:41:57 (I dont use IPK) Jul 07 09:42:27 bluelightning: nono, recipe's name is HmiFiles, but the warning is about HmiFiles-dev Jul 07 09:43:51 zero_note: don't know if it's causing the issue here, but I would strongly recommend using lowercase characters for the recipe name, uppercase will cause problems Jul 07 09:43:51 bluelightning: sorry, in fact I meant "the package simply fetch a tar.gz from git , unpack it and install the extracted files" Jul 07 09:44:00 zero_note: use 'oe-pkgdata-util list-pkg-files -p HmiFiles' to show what packages are generated and what is in them Jul 07 09:44:19 as an aside, we really need a QA check for that Jul 07 09:44:29 I may have filed a bug, can't recall Jul 07 09:45:10 bluelightning: really glad you pointed it out! Is there some filed bugs or documentation about uppercase named recipes problems? Jul 07 09:46:01 rburton: I've done it already, and everything seems as expected: PN installs the extracted files, PN-dev and PN-dbg are empty Jul 07 09:46:53 zero_note: https://bugzilla.yoctoproject.org/show_bug.cgi?id=11592 Jul 07 09:46:54 Bug 11592: enhancement, Medium, 2.4 M2, ee.peng.yeoh, NEW , Add QA check for uppercase recipe names Jul 07 09:49:24 bluelightning: oh, I am already subscribed to that bug :) Jul 07 09:50:27 from the description I can read: "uppercase characters in recipe names cannot be supported due to their reliance upon overrides including the name" Jul 07 09:53:23 does it mean that every use of ${PN} in a recipe with uppercase in its name could lead to problems? Jul 07 09:58:27 fixing that 11592 bug will increase the overall love for yocto as a whole ^^ Jul 07 10:09:53 zero_note: not necessarily, only if it appears in an override Jul 07 10:10:22 the package name overrides may still work as well thinking about it, since they may not be treated as overrides - I haven't checked the code Jul 07 10:10:31 well, as in FILES_ etc. Jul 07 10:10:48 _pn- overrides with PN containing uppercase definitely won't work anymore Jul 07 10:15:04 ed2: should all of ed/wip be good for merging? Jul 07 10:15:11 including the efi bits Jul 07 10:16:10 bluelightning: thats really interesting, I'll fix recipe's names and do a rebuild of that packages to see what happen Jul 07 10:16:11 rburton: no, it's not good. it still contains generic EFI changes waiting for Saul approval. Jul 07 10:16:32 i *think* sgw said we can merge and improve later Jul 07 10:17:48 rburton: and then he refused to take rmc patch. I reassigned generic EFI bug to him yesterday. He promised to look at it, but probably not in M2 time frame. Jul 07 10:17:51 can you split the efi patches out? the other patches depend on them, so i can't merge one without the others Jul 07 10:18:11 eg error: could not apply c1ab5f6f84e... image_types_wic: set default WKS_FILE_DEPENDS Jul 07 10:18:43 rburton: I'll split them and rebase on the latest master. Jul 07 10:18:54 rburton: after lunch if you don't mind. Jul 07 10:18:58 sure Jul 07 11:03:36 bluelightning: after a clenall of HmiFiles, renaming it as hmi-files, bitbake the image the "not found in the feeds" error has gone Jul 07 11:15:52 hi there im new to yocto. ive got your image on an imx6sx board, dhcp and need some packages to build gstreamer-imx. im really stuck Jul 07 11:16:26 braingain: ok, so what is the actual question? Jul 07 11:17:13 i need package management somehow Jul 07 11:17:47 sorry, but things dont work like "i just want to copypaste these two things and then you've got package management somehow" Jul 07 11:18:11 it works like: set up your build environment, and then create a image that contains what you need. Jul 07 11:18:34 thanks for clarification Jul 07 11:19:05 braingain : Do you have any yocto materials given by the vendor? Jul 07 11:19:12 so usually the board you have comes with some documentation on how to set up the fitting environment Jul 07 11:19:14 ChrysD: yes Jul 07 11:19:24 e.g., which layers and configuration items you need. Jul 07 11:19:27 braingain : are you using "meta-freescale" or meta-vendor Jul 07 11:19:42 its an udoo-neo board Jul 07 11:21:08 braingain : to be very brief. If you only want to do a job of integrator, you need to check first what is the linux kernel used and which version. Because depending of that you can't use gstreamer-imx Jul 07 11:21:15 rburton: done. ed/wip contains all my pending patches Jul 07 11:21:51 ChrysD: good heavens how did you know this? Jul 07 11:21:54 braingain : when I mean " you can't", i mean, if you just only want to do a job of integrator. Otherwise you will need to go in deep. Jul 07 11:22:08 braingain: go moan at the vendor: the yocto image seems to be download only and nowhere documented on the web page, it seems Jul 07 11:22:24 braingain : have you already setup the board and launch a kind of "demo" image? Jul 07 11:22:34 god my english is so bad Jul 07 11:23:07 (as long as they don't provide proper documentation and metadata, the yocto image is totally useless) Jul 07 11:23:33 yes ive been through a few built images. i know how do build kernels but i prefer not to. goal is to get gstreamer-imx to accept VADC analog video input and stream it via network Jul 07 11:24:57 braingain : so you are looking to put gstreamer-imx if it was a linux system such as " apt-get install" ? Jul 07 11:25:34 braingain : Because it can't be magical like that Jul 07 11:25:48 well i need an older version stored in github on https://github.com/dv1/gstreamer-imx Jul 07 11:25:50 braingain: my personal advice would be to use their ubuntu ripoff. the yocto image is useless and undocumented, and their github account doesn't seem to provide anything related to it. Jul 07 11:28:03 cant i build gstreamer-imx-plugins on another arm system and put binaries to yocto? Jul 07 11:28:21 not that easily, no. Jul 07 11:28:33 braingain : Is it mandatory to use yocto? Jul 07 11:29:05 it will at least take a lot more effort than taking ubuntu and hammering it long enough to compile whatever you need on the thing itself Jul 07 11:29:34 braingain : One other think. even if you success to put gstreamer-imx into your board, you are not sure that it works as you need maybe the freescale driver to make it working. Jul 07 11:29:48 braingain : if you use a old linux kernel version with a CODA driver you can't use gstreamer-imx for example. Jul 07 11:30:54 braingain : and I see on meta-udoo that the config of the kernel is using CODA... Jul 07 11:31:49 ah right, https://github.com/graugans/meta-udoo/wiki/Getting-started Jul 07 11:31:53 theres some docs Jul 07 11:32:06 funny they need to hide it under some non-corporate nickname Jul 07 11:32:33 you have also the readme of the meta-udoo which give some documentation Jul 07 11:32:41 but it's very light Jul 07 11:33:39 https://www.udoo.org/docs/Cookbook_Linux/Playing_video_with_GStreamer.html Jul 07 11:33:50 so basically it should be, set up your build environment according to that getting started page, and then add your needed packages Jul 07 11:33:58 When you use the UDOObunto 2.0 you can use gstreamer-imx Jul 07 11:34:19 UDOObuntu* Jul 07 11:34:27 hrhr Jul 07 11:34:32 -> ubuntu ripoff Jul 07 11:34:53 * LetoThe2nd sighs and is off into the weekend! Jul 07 11:35:23 keep cool ahahah Jul 07 11:36:11 I never said to not use udoobuntu, i just wanted to say that even if he have gstreamer-imx, maybe it won't work :) Jul 07 11:36:37 it sounds like it would actually make a lot of sense to use it for that specific case. Jul 07 11:36:50 having said that, time to leave. Jul 07 11:37:04 Have a good week end leto =) Jul 07 12:33:25 What MACHINE setting should I use for a regular PC? Such as an i5. I tried the genericx86, but bitbake tells me its an invalid setting Jul 07 12:41:40 Supposedly the meta-intel layer should support generic86, but it doesn't seem to include the .conf files Jul 07 12:44:13 christia3: intel-corei7-64 Jul 07 12:45:18 CTtpollard: Ill try that one and see how it works Jul 07 13:03:26 christia3: you need to add the right BSP layers to bblayers.conf. genericx86-64 is in meta-yocto-bsp, but a better one for you would be intel-corei7-64 from meta-intel Jul 07 13:03:26 when I am going to install Freescales imx-vpu i get to choose a Platform as in PLATFORM=IMX6Q. what is the short form of i.Mx6Solox? Jul 07 13:05:24 I am following build instructions from https://github.com/Freescale/gstreamer-imx/blob/master/docs/debian-ubuntu.md where they ask me to install the correct http://www.freescale.com/lgfiles/NMG/MAD/YOCTO/imx-vpu-5.4.31.bin for my platform Jul 07 13:55:37 hi o/ Jul 07 13:55:44 I'm looking for a help bbclass for luarocks Jul 07 13:55:49 do you heard about it? Jul 07 13:56:02 is there any documentation to make my own class for luarocks Jul 07 13:59:04 whats imx-vpu? Jul 07 14:05:00 rburton: Ah ok, I tried the i7-64 image from meta-intel and it works in my virtual machine with an .iso created with NOISO="0" Jul 07 14:05:22 I cannot see any hard drives though. Do I need to include a SCSI driver somehow? Jul 07 14:28:43 I fixed my problem by changing the hard drive type on my virtual machine to IDE instead of SCSI Jul 07 15:11:11 question on uninative ... so is there a way around the universal / universal-4.8 / universal-4.9 if you want to build-up a sstate-mirror for multiple hosts ? Jul 07 15:11:53 and do task hashes differ between a universal vs. universal-4.8 vs. universal-4.9 build ? Jul 07 19:00:00 So, Im trying to add support to a parallel CSI camera with a custom module on linux. Any tips on adding support for V4L2? Jul 07 19:00:29 I'm having a hard time figuring out which part of the ov driver is initialization, internal configuration, and v4l compatibility Jul 07 19:00:43 Do any of you know a minimal, no configuration driver ? Jul 07 19:02:47 anyone? Jul 07 19:03:32 CodeMaster_: This is probably the wrong IRC channel for that question Jul 07 19:04:15 Any channel you might recommend? Jul 07 19:04:33 Some kernel channel maybe? I wouldn't know Jul 07 19:04:39 sorry Jul 07 19:04:47 I'm back to freenode after several years lol so I've los a little track Jul 07 19:04:53 thanks jpew Jul 07 20:32:49 I'm making this recipe for a cmake project. The file executable in the build directory, but in my images rootfs, it's read only Jul 07 20:33:50 i've been looking at the bbclass and the cmakelists, but can't seem to see what I'm missing. Can anyone point me in the right direction? Jul 07 20:35:15 I've used chown on do_install() but i don't know if that is what you are looking for. Jul 07 20:35:22 mayble chmod works too Jul 07 20:39:13 yes, i did try chmod, but then i got a bunch of errors because it tried installing all the source files in the package Jul 07 20:40:38 not sure why it would do that. Jul 07 20:47:06 i was trying to just append the do_install Jul 07 20:47:31 but I see quite a few recipes that completely define do_install themselves, so maybe I should just do that... Jul 07 20:51:11 yeah i was referring to implement your own do_install Jul 07 20:52:05 chmod via a bbappend is best here **** ENDING LOGGING AT Sat Jul 08 03:00:00 2017