**** BEGIN LOGGING AT Thu Jul 30 02:59:58 2015 Jul 30 03:20:41 Fun... ERROR: Tried running useradd command 10 times without success, giving up -- that just started showing up on our 32 core builders in the last week or two: ~20150716 Jul 30 03:24:11 these systems are overloaded so we might have just exceeded the count of 10 due to an improvement in another part of bitbake/oe-core. Investigating. Jul 30 07:35:56 Hi, i have a question, i'm adding a 3.8 kernel recipe to meta-xilinx. I started using the same folder hierarchy from my meta-XXX folder. Just like i would do for a bbappend. I have everything (patches, config) but i can't find the way to tell bitbake to use my kernel. (and i don't even know if using the same hierarchy works for a bb file instead of bbappend ? ). I already used the COMPATIBLE_MACHINE. and now i must admi that i am a Jul 30 07:44:50 morning guys Jul 30 07:46:20 good morning Jul 30 07:56:16 Happycat: you need to set PREFERRED_PROVIDER_virtual/kernel to point to your custom kernel recipe. Jul 30 07:59:49 Ok, so i have to change my recipe, now i have the same name and hierarchy as meta-xilinx. I must have my own kernel name and hierarchy so ? Jul 30 08:04:23 Happycat: not sure what you are calling a hierarchy? is that a layer? Jul 30 08:05:37 Yes, by hierarchy i mean if i have a X.bb in a recipes-nothing folder inside a meta-something i create a meta-mylayer inside it i put recipes-nohing and my X.bbappend in it. Jul 30 08:06:08 It's asking me for a LICENSE, i must have mistaken somewhere Jul 30 08:06:49 so, what you want to do is make your own custom kernel recipe (which doesn't exist yet), right? Jul 30 08:07:26 i am confused by your reference to .bbappend Jul 30 08:09:48 Yeah sorry , it was a bad explanation :/, I want to add my kernel recipe for a 3.8 kernel. (currently meta-xlnx only provide 3.14 and 3.19 kernel). But i don't want to edit the meta-xlnx layer. I'd like to use several .inc that i found inside it. So i did just like i would with a bbappend, i didn't want to override anything else that the version of the kernel. Preventing it to build a 3.14 / 3.19 and build mine without touching a s Jul 30 08:10:35 Happycat: you can't override the 'version' with a .bbappend Jul 30 08:11:03 .bbappend is only to make modification in an existing recipe. what you need is a new recipe. Jul 30 08:11:27 you can make your own layer with meta-foo/recipes-kernel/xxx/yyy.bb Jul 30 08:11:35 and you can include the .inc from meta-xilink Jul 30 08:11:44 Yeah i know, arg i don't know how to explain it :p ndec that is what i did exactly ! Jul 30 08:12:07 well, then that's good ;-) Jul 30 08:12:33 i don't have bbappend, i mean i used recipes-kernel/linux/linux-xlnx_3.8.bb Jul 30 08:12:47 well i created it. Jul 30 08:12:57 ok, does your recipe build, at least? Jul 30 08:13:21 It is asking me for a license, but i'm confuse i thought i would detect a kernel recipe and don't ask for a license , no ? Jul 30 08:14:06 every recipe needs to set LICENSE. Jul 30 08:15:03 really ? but i didn't see any LICENSE in the linux-xlnx 3.14 or 3.19 recipe. i'll check again so :) Jul 30 08:16:21 it's in linux-yocto.inc which is included Jul 30 08:17:45 Ok i see it :) thanks so i have to figure out why it's not included Jul 30 08:18:11 it sould be as i'm using the .inc from linux-xlnx Jul 30 08:20:46 Happycat: looking at linux-xlnx.inc , i am not sure you can include it in a separate layer, though. it wouldn't find "require linux-xilinx-configs.inc " Jul 30 08:23:03 Ok, i was wondering why it wasn't working , why can't i include it ? So creating my own recipe not using linux-xlnx.inc would be the only possible sollution ? Jul 30 08:24:31 if you 'include' the file, then when it is parsed it will try to process the included file which has "require linux-xilinx-configs.inc", so it will try to load this file too, but it cannot find it. Jul 30 08:25:42 ok :/ so it would be mandatory to put my recipe in linux-xlnx folder (inside meta-xlxn).. i have to check if it would be acceptable :/ Jul 30 08:25:47 thanks a lot for the help :) Jul 30 08:26:11 well, the meta-xlinx .inc file could be patch to allow what you want to do. Jul 30 08:26:54 require recipe-kernel/linux/linux-xilinx-config.inc , should work. Jul 30 08:38:37 Yeah but isn't the configuration process based on config fragments ? i have a full defconfig , i thought it was incompatible with fragments no ? Jul 30 08:39:36 hmm, any documentation for bitbake-whatchanged beyond the commit logs? Jul 30 08:39:46 it doesn't appear to be mentioned in the ref-manual or dev-manual Jul 30 08:43:11 it is indeed 'incompatible' Jul 30 08:43:15 pls read meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb Jul 30 08:45:47 morning all Jul 30 10:12:49 guys, it there a posibility to print out from which commit yocto fetches changes for particular package? Jul 30 10:31:22 hi guys Jul 30 10:31:35 i am getting a build failure on the master branch Jul 30 10:31:47 the do_install step for python fails Jul 30 10:32:12 Illegal instruction (core dumped) Jul 30 10:32:13 make: *** [sharedmods] Error 132 Jul 30 10:32:13 ERROR: oe_runmake failed Jul 30 10:40:05 abelal: debug it Jul 30 10:40:14 abelal: do you have core dumps? Jul 30 10:40:33 Ox4: I am trying to I do not get the core dump Jul 30 10:41:02 Ox4: i will be trying the devshell to see if I get anything more Jul 30 10:41:19 abelal: good boy :) Jul 30 10:41:24 Ox4: how can I make 'make' more verbose Jul 30 10:41:27 ? Jul 30 10:41:56 for bitbake? Jul 30 10:42:03 -vDDD Jul 30 10:42:12 nope when i am in the devshell Jul 30 10:42:21 i should say make -vDDD Jul 30 10:42:22 but I suggest to redirect it to a file Jul 30 10:42:22 ? Jul 30 10:42:26 ok Jul 30 10:42:28 nope Jul 30 10:42:48 abelal: what are you going to do in the devshell? Jul 30 10:43:12 Ox4: I would run the make command that fails in the do_install process Jul 30 10:43:19 to see if it gives anything more Jul 30 10:43:33 but I would like to see 'make' being more verbose about all it Jul 30 10:43:51 because although it says core dumped i am not getting any dumps Jul 30 10:45:45 abelal: the you have to set V=1 in the makefile Jul 30 10:45:59 sorry not in the make Jul 30 10:46:05 makefile* Jul 30 10:46:11 just add V=1 as a parameter Jul 30 10:48:13 Ox4: i should probably simply add it to EXTRA_OECMAKE? for python Jul 30 10:49:12 abelal: I thinks yes Jul 30 10:50:44 Ox4: i am getting "[ 4530.844683] traps: python2.7[22442] trap invalid opcode ip:2b9e9153ec54 sp:7ffc1f5b13f0 error:0 in strop.so[2b9e9153d000+6000] Jul 30 10:50:45 " in my dmesg Jul 30 10:51:12 possibly a host side issue as the same build runs fine on another host Jul 30 10:51:22 interesting Jul 30 11:06:14 abelal: whish system are you using? Jul 30 11:06:37 Ox4: it's a Ubuntu 14.04 system Jul 30 11:06:45 which kernel? Jul 30 11:06:52 Ox4: i have python 2.7.6 installed Jul 30 11:07:10 Ox4: 3.13.0-61-generic Jul 30 11:07:28 so ancient :-( Jul 30 11:07:55 anyway if you run some python script is it executed successfully? Jul 30 11:10:45 Ox4: no issues with python... not on host console neither in devshell Jul 30 11:18:11 hey, I wonder if reboot could be moved to busybox.suid? Jul 30 11:18:35 I wish to be able to reboot the board as some dedicated user. Jul 30 11:19:06 currently, we use our own suid reboot binary, but to be fair, since these days busybox seems to be split into two parts with Yocto, I wonder if it makes sense or that still cannot help us? Jul 30 11:19:43 Any idea why my oprofile package is not shiping opcontrol or operf? Jul 30 11:29:17 well, anyway, we can certainly override what goes into non-suid and suid? Jul 30 12:58:55 Can I say build from a tag defined as parameter, or will it always build from the given branch given in the conf? Jul 30 13:09:52 AzaToth_: http://docs.openembedded.ru/src_uri_variable.html Jul 30 13:21:33 the qemuarm64 sanity test failure appear to be a host configuration error: | (qemu) qemu:qemu_cpu_kick_thread: No such processReleasing lockfile of preconfigured tap device 'tap1' Jul 30 13:27:07 Will pidge handle that once the west coast of NA wakes up.I'm trying to figure out who is involved in maintaining system sanity so that I can pitch in.... Jul 30 13:28:56 pidge is in GMT Jul 30 13:29:10 AzaToth_: I don't follow. You can checkout your oe-core /bitbake/ foo layer to whatever commit/tag/branch you like. Of course only certain configs are sane... Jul 30 13:30:22 rburton: ok. no pidge in the channel. Who can confirm that the build failure is due to an error in the buildbot config and fix it? Jul 30 13:32:44 lpapp: reboot should not be suid as a default. You should make that change locally if that makes sense for your work. Jul 30 13:33:05 someone rang? Jul 30 13:34:08 vmeson: what suggests to you that that's a configuration error ? Jul 30 13:34:10 Hi pidge. I'm trying to help out with some of the autobuilder errors. Be patient as I learn how the YP AB works.. Jul 30 13:35:11 I just guessed that tap0 would be the default device used.... qemu) qemu:qemu_cpu_kick_thread: No such processReleasing lockfile of preconfigured tap device 'tap1' Jul 30 13:35:59 it uses tap[n] based on the number of concurrent qemus running right? Jul 30 13:36:00 vmeson: are you seeing this on the main AB? Jul 30 13:36:10 I'll be spending some time getting buildbot and YP AB running locally but I havent' done that yet... Jul 30 13:36:18 pidge: yes: [07:33] [Notice] -YoctoAutoBuilder to #yocto- build #76 of nightly-arm64 is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/76 Jul 30 13:36:39 rburton: yes. We generally use the setup tap script in poky. let me take a look at this... Jul 30 13:37:16 * vmeson reads the error message again and reconsiders his assumption... Jul 30 13:38:49 vmeson: well, remember. One autobuilder may be running a whole lot of qemu sessions. I forget how many taps we set up but it's quite a few. 24? Jul 30 13:39:29 vmeson: "qemu:qemu_cpu_kick_thread: No such process" suggests to me a qemu bug Jul 30 13:40:18 bluelightning: yeah. I've had some coffee now. I agree. I'll see if I can reproduce the error locally. Jul 30 17:19:22 hmmm Jul 30 17:58:08 <[Sno]> is it possible (and if: how) to use a yocto-builddir for two machines (first build for machine A, then for machine B)? Jul 30 17:59:45 [Sno]: yes, and just change MACHINE value (or ensure it's set with ?= in the configuration and then pass it in from the external environment) Jul 30 18:00:22 bbl Jul 30 19:05:41 hi i am looking for help with installation to an SSD. Jul 30 19:09:58 Hi everyone, I created a new stackexchange proposal. Can you guys please vote? http://area51.stackexchange.com/proposals/89593/yocto?referrer=Gl65yCKrZ2GVxRQFferA1Q2 Jul 30 20:16:52 hello Jul 30 20:18:15 i'm trying to pull down a file and I get a checksum error. It says this error can be avoided by adding lines to your recipe. It gives some lines to add , but I don't know where to add these lines? in the layer.conf for this recipe or in a config file in poky tree? Jul 30 20:21:30 also, I'm using hob and I can not copy and paste the log ocmments from the issue message list. Is this log kept someplace in file system? I see a bunch of .log files in build/tmp/work but nothing for this particular package. Jul 30 20:23:03 ahh, i found it. poky/tmp/log/cooker/beaglebone/*.log Jul 30 20:25:46 i added the log suggestion to meta-oracle-java/conf/layer.conf as a hail mary. perhaps I'll get lucky. Jul 30 20:40:52 so this seems to be building the java package. Jul 30 20:42:41 I'm also trying to get the lcd cape working. Currently it does not. dmesg shows drm (direct rendering module) for a tilcdc driver. I'm guessing that is Texas Instruments lcd controller. Jul 30 20:43:02 so maybe the lcd is in the kernel, but it needs something in userspace to enable it. Jul 30 20:43:46 is there a package for the sato recipe which needs to be modified to specify a 4D systems LCD cape? its something I got from sparkfun or adafruit. Jul 30 20:59:02 is there a way to config the kernel config via hob? Jul 30 22:00:29 hello i am trying to install my core-image-sato image to a SSD that i partition... Jul 30 22:00:42 is there already a standard script or process for this? Jul 30 22:01:23 tried the instructions here: https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_put_Yocto_on_a_hard_drive.3F Jul 30 22:02:16 but the grub-install failed with "grub-install: error: /mnt/target doesn't look like an EFI partition." Jul 30 22:03:03 i am trying to install to a big SSD, i want to have some data and backup partitions on it too.. so i should just be able to use the ext3 and then configure grub... Jul 30 22:03:28 i found some scripts that look like install scripts in initrd recipes in poky i think... i need to go and look again Jul 30 22:03:36 i was also wondering what the iso is for Jul 30 22:05:51 any advice?? Jul 30 22:08:36 I usually populate the partiton (un tar into it) and then chroot into it and run grub from there. Jul 30 22:09:04 you have to mount dev and proc in the chroot to keep grub2 happy. and this assumes grub is in your installed fs. Jul 30 22:10:42 there are probably more user friendly ways to do it ; I just do that because that is what I've done since the beginning of time ; before yocto even existed. Jul 30 22:11:31 a system rescue CD (on USB key) is a good way to bootstrap so you can untar and populate the partitions IMHO Jul 30 22:11:53 system rescue assumes x86 of course. Jul 30 23:57:55 hm ok thanks paulg thinking about your answer. yeah i have used chroot before, it sounds like that might work Jul 30 23:58:13 let me see if i have grub installed and try. maybe i will try syslinux also Jul 31 01:45:56 https://twitter.com/SwiftOnSecurity/status/626927142916362240 <-- this is possibly one of the most beautiful things i have ever read **** ENDING LOGGING AT Fri Jul 31 02:59:58 2015