**** BEGIN LOGGING AT Sat Jun 21 03:00:00 2014 Jun 21 06:31:22 hi.any body here Jun 21 06:31:27 ? Jun 21 06:34:53 I want to run bitbake command in a script. but it has an error... the error is "classes/rpm.bbclass"!!!. In poky-dora release, this class doesn't exist!!!! but it want to inherit from it! & I don't know how to fix this. anybody any solution? Jun 21 06:39:58 sm_: well, take a look at the entire output. It will tell you _which_ file tried to inherit that. Is this one of your files? Jun 21 06:46:11 zecke: thanks for respondig. my error log is: Jun 21 06:46:14 ERROR: Traceback (most recent call last): File "/home/bitbake_user/Release/poky-dora-10.0.1/bitbake/lib/bb/cookerdata.py", line 162, in wrapped return func(fn, *args) File "/home/bitbake_user/Release/poky-dora-10.0.1/bitbake/lib/bb/cookerdata.py", line 176, in _inherit bb.parse.BBHandler.inherit(bbclass, "configuration INHERITs", 0, data) File "/home/bitbake_user/Release/poky-dora-10.0.1/bitbake/lib/bb/parse/parse_py/BBHand Jun 21 06:47:47 include(fn, file, lineno, d, "inherit") File "/home/bitbake_user/Release/poky-dora-10.0.1/bitbake/lib/bb/parse/parse_py/ConfHandler.py", line 100, in include raise ParseError("Could not %(error_out)s file %(fn)s" % vars(), oldfn, lineno) ParseError: ParseError in configuration INHERITs: Could not inherit file classes/rpm.bbclass ERROR: Unable to parse rpm: ParseError in configuration INHERITs: Could not inherit file classes/r Jun 21 06:51:39 sm_: use something like pastebin or paste.lisp.org for pasting the full log Jun 21 06:51:48 sm_: well. you have INHERIT += "rpm" in your local.conf? Jun 21 07:11:19 zecke: no, there isn't. Jun 21 07:14:02 aaaaaaa. YESSSSS Jun 21 07:14:22 zecke: you're right!!! Jun 21 07:14:51 zecke: that was the problem :). thank you Jun 21 09:17:26 Hi, I try to build a small image based on yocto-tiny. However the init process does not start (Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004). Jun 21 09:17:27 Is there any way I can get a more verbose error message, or an other way to solve my issue? Jun 21 09:17:36 boot log: http://pastebin.com/L5L7G4Hc Jun 21 09:18:20 I already tried to switch from tiny-init to busyboy-based init but the error remains the same Jun 21 12:03:01 Good morning #yocto. :) That is all. Jun 21 12:10:59 I created a .bbappend file, and it's being parsed. In that .bbappend I have SRC_URI += "file://linux-steve.cfg" I get an error that my file isn't found, and the directory it's in is not in the list of paths that were searched. What is the proper way to specify the path, which is in my own little layer? Jun 21 12:12:02 This is a new kernel configuration "fragment". (It's actually the whole damn config, which might not work but I don't think I'm that far yet) Jun 21 12:12:57 zman97211: you can add paths searched by using FILESEXTRAPATH Jun 21 12:14:06 Ok. I assume using the += operator to add the path. Is there a list of variables I can use in the path name so it's portable? Jun 21 12:14:26 http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-FILESEXTRAPATHS Jun 21 12:14:54 Perfect thank you! Jun 21 12:14:54 you can use any variable available through bitbake i guess Jun 21 12:15:17 Yes, but there are so many I don't want to get it wrong. That gives an example of relevant ones though. Cool. Jun 21 12:45:53 seezer thank you. I got it working. Jun 21 12:55:04 you're welcome Jun 21 13:48:36 I rebuilt my image, and the kernel that was included in /boot did not change, even though I supposedly included a whole new kernel configuration. Can a kernel config fragment be an entire .config file? Jun 21 13:49:25 When I baked my image, it did run tasks to rebuild the kernel. Jun 21 13:50:39 It's like the .bbappend I made triggered the rebuild but had no effect. Jun 21 13:54:20 If a file mentioned in SRC_URI isn't found, is that an error or is it just ignored? Jun 21 17:42:12 zman97211: don't use += for FILESEXTRAPATHS, it's colon separated, not space :) Jun 21 17:42:18 error Jun 21 17:52:30 kergoth: I'll give that a shot. Jun 21 17:52:41 search for examples. there are plenty around Jun 21 17:54:30 This is what I have, and it was copy/pasted from the reference manual. I don't think this is the problem, because it's finding my .cfg file, it just doesn't appear to use it. Jun 21 17:54:36 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" Jun 21 17:55:48 a grep of "meta" shows they all use "=." instead of ":=" Jun 21 17:57:03 and without the _prepend Jun 21 17:57:25 The manual differs from reality lol Jun 21 17:59:10 I did get a warning about not finding a checksum for my .cfg file. If it doesn't find one, does it not apply it? Jun 21 17:59:43 And when I changed my .bbappend to use =. instead of _prepend :=, it can't find my .cfg file again. Jun 21 18:03:26 which kernel is this? Jun 21 18:03:34 not all kernels support config fragments Jun 21 18:03:38 linux-yocto does Jun 21 18:06:29 linux-raspberrypi Jun 21 18:08:01 from http://git.yoctoproject.org/cgit.cgi/meta-raspberrypi/ Jun 21 18:15:00 if it doesn't inherit kernel-yocto, it likely doesn't support kernel config fragments at all. if they use file://defconfig in the SRC_URI for the config, you could override that by putting your own file named defconfig where you put the .cfg, and don't modify SRC_URI at all in your bbappned Jun 21 18:37:48 You're saying put my .cfg file in their layer instead of my own, or just pu a defconfig.cfg in the exact same place as my config already is?? **** ENDING LOGGING AT Sun Jun 22 02:59:58 2014