**** BEGIN LOGGING AT Mon Mar 30 02:59:59 2015 Mar 30 08:21:18 good morning Mar 30 08:44:23 hello Mar 30 08:44:44 I'd like to modify u-boot options to add this : setenv mmcargs 'setenv bootargs console=ttymxc0,115200 root=/dev/mmcblk2p2 rootwait rw video=mxcfb0:dev=hdmi, 1920x1080M@60, if=RGB24' Mar 30 08:45:04 The best would be to do it with a recipe, but I didn't find a clue. Mar 30 08:45:21 I found this : https://community.freescale.com/thread/324811 Mar 30 08:45:45 But it's pretty difficult, and to general (modify u-boot for all the builds). Mar 30 11:17:24 Hi Mar 30 11:17:38 I'm looking for a way to create boot.scr Mar 30 11:17:55 To add this to uboot : setenv mmcargs 'setenv bootargs console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=hdmi, 1920x1080M@60, if=RGB24' Mar 30 11:41:21 <_4urele_> eMazo, I have a recipe that depends on : ''DEPENDS = "u-boot-mkimage-native"'', and in the do install : Mar 30 11:41:24 <_4urele_> uboot-mkimage -A arm -T script -C none -d ${WORKDIR}/env.txt ${WORKDIR}/bootscript-${MACHINE} Mar 30 11:41:38 <_4urele_> cp ${WORKDIR}/bootscript-${MACHINE} ${D}/boot/boot.scr Mar 30 11:42:03 <_4urele_> (maybe install would be better ;) ) Mar 30 11:43:25 _4urele_: so, in your env.txt, you put what ? Mar 30 11:43:36 setenv mmcargs 'setenv bootargs console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=hdmi, 1920x1080M@60, if=RGB24' ? Mar 30 11:44:26 <_4urele_> I have something like that Mar 30 11:45:26 <_4urele_> eMazo, depends on what you have in your compiled u-boot Mar 30 11:45:42 <_4urele_> eMazo, I would say : setenv bootargs console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=hdmi, 1920x1080M@60, if=RGB24 Mar 30 11:46:03 <_4urele_> or setenv mmcargs console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=hdmi, 1920x1080M@60, if=RGB24 Mar 30 11:46:40 <_4urele_> or also setenv bootargs ${mmcargs} Mar 30 11:47:19 _4urele_: I add the part : video=mxcfb0:dev=hdmi, 1920x1080M@60, if=RGB24 Mar 30 11:47:33 It's for activate HDMI. Mar 30 11:50:55 <_4urele_> eMazo, it is like a script, I don't know how the boot.scr is read, you have to read how the platform use this Mar 30 11:51:34 <_4urele_> (it is in an include file, It should not be difficult to understand Mar 30 11:51:44 <_4urele_> what machine are you using? Mar 30 11:56:23 _4urele_: Freescale i.mx6 Mar 30 12:08:24 <_4urele_> eMazo, and th name of the defconfig? Mar 30 12:09:41 _4urele_: what's that ? (sorry ^^') Mar 30 12:19:05 <_4urele_> the name of your evaluation board? Mar 30 12:19:17 <_4urele_> the name of your evaluation board Mar 30 12:19:24 <_4urele_> eMazo, Mar 30 12:25:31 _4urele_: imx6qsabresd Mar 30 12:30:29 <_4urele_> eMazo, take a look at : http://git.denx.de/?p=u-boot/u-boot-imx.git;a=blob;f=include/configs/mx6sabre_common.h;h=b72522bf522d38b11151b4dff47aa57c4a24c796;hb=HEAD Mar 30 12:33:01 <_4urele_> eMazo, according to this file, I would say you should add "loadimage" and "run mmcboot" to your script Mar 30 12:33:49 I try Mar 30 12:34:09 <_4urele_> eMazo, as you can see at line 199 with the "CONFIG_BOOTCOMMAND" your script will replace the complete default command Mar 30 12:37:08 <_4urele_> eMazo, check this : http://paste.ubuntu.com/10706478/ (maybe it will work out of the box, maybe you will have to tweak it ;) ) Mar 30 12:41:51 _4urele_: uboot doesn't know loadimage Mar 30 12:42:30 Seems that I will have to tweak it. I'm trying to do that since this morning, still no clues :/ Mar 30 12:44:45 <_4urele_> eMazo, I brought the latest u-boot config you chould check in your version of u-boot Mar 30 12:45:06 The latest too. Mar 30 12:45:21 I've cloned the git repo last week. Mar 30 12:45:57 <_4urele_> did you tried to manualy launch those lines? Mar 30 12:46:28 manually, I do : Mar 30 12:46:31 setenv mmcargs 'setenv bootargs console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=hdmi, 1920x1080M@60, if=RGB24' Mar 30 12:46:33 saveenv Mar 30 12:46:35 boot Mar 30 12:47:45 <_4urele_> try to don't call boot :) try with loadimage Mar 30 12:48:02 <_4urele_> (or "run loadimage"?) Mar 30 12:48:49 <_4urele_> look at CONFIG_BOOTCOMMAND to see what "boot" does Mar 30 12:51:01 <_4urele_> eMazo, i forgot the "run" before loadimage... (as it is written in the "CONFIG_BOOTCOMMAND" Mar 30 12:51:08 Hi, a colleague of mine got this error while building yasm in poky a few days ago: configure.ac:99: error: possibly undefined macro: AM_WITH_DMALLOC | If this token and others are legitimate, please use m4_pattern_allow. Mar 30 12:51:31 I am not able to reproduce it now, but I read several topics on the internet Mar 30 12:51:48 and it seems related to AC stuff being read from aclocal.m4 which gets deleted at some point in build Mar 30 12:51:57 and I saw several recipes copying the file to acinclude.m4 Mar 30 12:52:12 can someone give me five cents on wheter that should be done for yasm? Mar 30 12:52:21 it is indeed reading from aclocal.m4 too Mar 30 12:55:48 <_4urele_> eMazo, did it worked? Mar 30 13:01:35 does anyone know if there is a release review of Dizzy where the new features are explained etc - maybe someone commenting this new release in a blog post, or anything like that , thank you ;) Mar 30 13:15:37 _4urele_: thanks a lot, it worked ! Mar 30 13:22:02 is there a tool to get the patches for a particular board extracted from either yocto or somewhere else ? Mar 30 13:24:09 or a recipes that will prepare an OpenWRT compatible target ? Mar 30 13:25:25 nighty-_: unfortunately not, I'd love to have it too Mar 30 13:25:41 mckoan, :( Mar 30 13:26:19 nighty-_: perhaps you're asking too much :-) Mar 30 13:26:29 mckoan, what do you mean ? Mar 30 13:26:45 nighty-_: OpenWRT is a completely different build system Mar 30 13:26:56 mckoan, yeah well not my fault vendors are stupid Mar 30 13:27:09 mckoan, they provide a yocto SDK Mar 30 13:27:17 mckoan, and not even a set of patches Mar 30 13:27:36 mckoan, you have to play find me games to find the relevant patches Mar 30 13:27:56 mckoan, that apply to a particular SoC and board Mar 30 13:28:13 because they do not upstream it Mar 30 13:28:40 ie: Freescale Mar 30 13:29:29 I never asked to be using yocto Mar 30 13:29:38 that is a bit forced upon me Mar 30 13:29:46 reason above Mar 30 14:57:55 anyone know how to fix these cross compile issues? it's looking in /usr/local/include, do i need to pass something to EXTRA_OECONF? http://pastebin.com/X3T1cLQY Mar 30 15:01:09 cgkades: its probably finding a dependency it needs in /usr/local, read the configure output and see if you can figure out what it is Mar 30 15:01:20 then you can either add it as another dependency, or add options to disable it Mar 30 15:01:48 though some build scripts do stupid things like add /usr/local to the link path automatically, which is dumb and needs to be patched out Mar 30 15:02:41 rburton: i'm new to autotools so i'm not really sure what i should be looking at. Mar 30 15:03:01 would it be manually linked in the configure.ac? Mar 30 15:03:38 that's where you'd be looking, yeah Mar 30 15:03:44 reading the configure output should give you a hint Mar 30 15:05:22 output from ./confgiure? or autoconf? Mar 30 15:05:29 configure Mar 30 15:05:38 ok, i'll check it out, thanks Mar 30 15:05:43 have a look in temp/log.do_configure and search for local Mar 30 15:09:47 in do_configure i see —libdir=/usr/lib Mar 30 15:11:18 that's right Mar 30 15:11:35 http://pastebin.com/p5kVRJh8 Mar 30 15:12:26 hm Mar 30 15:12:28 1. ERROR: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities. Mar 30 15:12:28 2. Rerun configure task after fixing this. The path was '/home/byoakum/galileo/meta-clanton_v1.1.0-dirty/yocto_build/tmp/work/i586-poky-linux/gphoto2/2.4.11-r5/gphoto2-2.4.11' Mar 30 15:12:53 i wonder if i broke that Mar 30 15:13:19 i think it errors when it see's the cross compile error right? Mar 30 15:13:55 yeah i broke it Mar 30 15:13:57 damns Mar 30 15:14:45 what'd you break? Mar 30 15:14:45 go to that directory, find the config.log file in a subdirectory Mar 30 15:14:52 i broke the test, it's reporting the wrong path Mar 30 15:16:01 tmp/work/i586-poky-linux/gphoto2/2.4.11-r5/gphoto2-2.4.11/ is where the log file is Mar 30 15:16:05 then grep that file for "Badness" Mar 30 15:16:40 doesn't find anything Mar 30 15:16:49 try "unsafe" Mar 30 15:17:13 yeah. finds the warnings i put up earlier Mar 30 15:17:23 cc1: warning: include location "/usr/local/include" is unsafe for cross-compilation [-Wpoison-system-directories] Mar 30 15:17:31 at configure time?! Mar 30 15:17:40 hm wasn't expecting that tbh Mar 30 15:17:42 pastebin the entire file please Mar 30 15:17:50 the config.log? Mar 30 15:18:18 http://pastebin.com/k01Fj17e Mar 30 15:22:49 do you expect gphoto to link with cdk? Mar 30 15:23:01 what is cdk? Mar 30 15:23:26 no idea ;) Mar 30 15:23:36 hah ok Mar 30 15:23:47 add —without-cdk to EXTRA_OECONF Mar 30 15:23:57 ok i'll try that Mar 30 15:24:23 hm, its trying that path for all the tests Mar 30 15:25:27 is it ok that i's pointing to the system dir's instead of a sysroot for everything? like libdir is /usr/lib and sysconfdir is /etc Mar 30 15:25:49 still broken with the —without-cdk Mar 30 15:26:08 yeah, you tell it sysconfdir is /etc and then point at a sysroot for linking Mar 30 15:26:50 is that pointing done by yocto magic? or is it something i have to do/pass somewhere Mar 30 15:26:55 yes, its magic Mar 30 15:27:02 ok Mar 30 15:27:07 oh look gphoto explicitly adds /usr/local/lib to teh search path for fun Mar 30 15:27:31 sweet Mar 30 15:27:50 is that in the configure.ac? Mar 30 15:28:11 not explicitly Mar 30 15:28:28 is there a m4m folder under configure.ac? Mar 30 15:28:40 ls Mar 30 15:29:11 yeah Mar 30 15:29:52 open m4/gp-check-library.m4, search for /usr/local/lib and delete all the paths that don't start with a variable Mar 30 15:30:11 there's a loop something like for _libdir_ in Mar 30 15:30:29 god this is idiotic Mar 30 15:30:43 welcome to a week of my life Mar 30 15:30:47 :) Mar 30 15:31:39 ok i see what you're talking about in there. i'll create a patch Mar 30 15:31:50 this is the sort of nonsense that maintainers think is clever, but is actually dumb Mar 30 15:32:51 hardcoding anything is bad… good thing we have plenty of examples on why…… Mar 30 15:38:49 Hi there, I have some problem with kernel configuration after migration from 1.6 to 1.7. Mar 30 15:39:20 In 1.6 a defconfig file was used together with to config fragment files. Mar 30 15:39:56 Since 1.7 the defconfig is no longer used for the .config generation. Mar 30 15:49:58 it's less broken now Mar 30 15:51:08 now it's mad about hard coded /usr/local/include Mar 30 15:51:24 ha Mar 30 15:51:51 3 places instead of 5 Mar 30 15:51:55 PROGRESS! Mar 30 15:54:00 hahaha Mar 30 15:54:03 i like your attitude :) Mar 30 15:54:22 :) Mar 30 15:54:54 reckon you can chase that one yourself? All the horror is probably in m4/ Mar 30 15:54:58 any pointers on where it's getting this value? i'm not seeing anything in m4m Mar 30 15:55:13 or i'll even take a way to override it Mar 30 15:55:25 so its the jpeglib test thats triggering Mar 30 15:56:11 configure:15348: i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/byoakum/galileo/meta-clanton_v1.1.0-dirty/yocto_build/tmp/sysroots/quark -c -O2 -pipe -g -feliminate-unused-debug-types -I/usr/local/include conftest.c >&5 Mar 30 15:56:14 based on that? Mar 30 15:56:56 yeah, the line above says what the test was Mar 30 15:57:44 conftest.c? but where is it filling in the values for -I? Mar 30 15:58:33 no idea right now Mar 30 15:58:53 ok phew.. i thought i was the only one :) Mar 30 15:59:45 might have found it with grep -r usr * | grep include Mar 30 16:04:51 is there a $includedir variable for the .bb files? Mar 30 16:06:03 yes, and its passed to configure for you Mar 30 16:06:12 line 7 of your log, --includedir Mar 30 16:06:51 and it's passing the wrong dir, right? Mar 30 16:07:17 nope Mar 30 16:07:58 but the config.log is complaining that /usr/local/include is bad for cross compile Mar 30 16:08:05 yes Mar 30 16:08:42 ah, and that' s different from what is actually being passed Mar 30 16:14:53 cgkades: can you pastebin the gphoto2_2.4.11.bb file? Mar 30 16:15:13 morning.. Mar 30 16:15:32 yeah Mar 30 16:15:58 hi fray Mar 30 16:16:16 rburton: http://pastebin.com/MvNBBe7p Mar 30 16:17:08 cgkades: did you write that or is it part of the galileo sdk? (can you tell i've not unpacked mine) Mar 30 16:17:25 i wrote it Mar 30 16:17:42 based off of the libgphoto2 from openembeded Mar 30 16:18:29 remove the do_configure_append bit Mar 30 16:18:52 ok Mar 30 16:19:15 i think it wouldn't work if i didn't have that there. but i'll try it Mar 30 16:19:56 it would, because that's running after it ran configure the first time ;) Mar 30 16:20:23 ah ok. then i fixed what was wrong at the same time i added that Mar 30 16:20:31 still broken though Mar 30 16:21:32 not a new broken… the same /usr/local/include broken Mar 30 16:21:57 * nerdboy got the rpi-2's while busy being annoying at oedam Mar 30 16:22:38 new device tree stuff and everything... Mar 30 16:23:52 * nerdboy also running out of suitable microsd's Mar 30 16:38:39 in case anyone else ends up needing it: DATETIME_SECS = "${@int(time.mktime(time.strptime('${DATETIME}', '%Y%m%d%H%M%S')))}" Mar 30 16:42:09 cgkades: no idea, sorry. you might be left tracing the configure script to see where /usr/local/include appears Mar 30 16:42:46 rburton: ok thanks for the help though :) how do you trace that configure script? Mar 30 16:43:40 grep might be quicker... Mar 30 16:43:43 cgkades: read it to see if there's any uses directly, or else try and work out where it appears and if a previous command could have added it to include paths Mar 30 16:43:53 (worst bit about software is building the damn stuff) Mar 30 16:44:46 anything with 'usr/local' should stick out like a sore thumb... Mar 30 16:45:08 yeah, that's what has been killing me with this yocto project. I need to add so much for what i'm trying to do. and running into issues not only with the software but with a whole new build system Mar 30 16:49:21 it's certainly annoying when you try and build something that should be trivial but software is just broken Mar 30 16:49:38 might be worth upgrading that version to a recent one and seeing if that helps - 0.4.11 is several years old Mar 30 16:51:13 yeah, it's just that openembeded had that version for libgphoto. i'll try to rebuild that one as well now that i'm a little more familiar with the recipes Mar 30 17:35:06 * cgkades1 bashes head into desk Mar 30 17:35:16 /bin/sh: 0: Can't open @MKINSTALLDIRS@ Mar 30 17:37:54 * nerdboy got some notice at scale => https://lwn.net/Articles/635289/ Mar 30 17:38:04 hth did that happen? Mar 30 17:43:06 good article about the problem.. Mar 30 17:58:33 is it just me or the behaviour of "inherit autotools" have changed in Dizzy ? and is there somewhere online I can read about theses changes in dizzy versus daisy ? Mar 30 18:01:37 acidfu: the ref manual has a section "Migrating to a Newer Yocto Project Release" Mar 30 18:02:24 oh great I'll read that Mar 30 18:02:25 thank you Mar 30 18:02:30 fray: he mixed up a few details, but stephanie seemed to like it Mar 30 18:08:09 yup Mar 30 18:08:40 I'd say most of hte comments equally apply to any embedded process.. not just ARM.. graphics, modules and kernel versions are a nightmare.. Mar 30 19:30:04 I would like to kindly ask for some help in trying to enable ntfs mount support on core-image-base by using ntfs-3g-ntfsprogs. From the build log it appears that the ntfs-3g does build, but it is not present in the final image. Mar 30 19:30:09 ntfs-3g-ntfsprogs recipe is here: http://pastebin.ca/2966651 Mar 30 19:30:15 The build log is here: http://pastebin.ca/2966653 (search for ntfs-3d) Mar 30 19:30:21 The recipe suggest the final froot file system should have a sbin/mount.ntfs link to mount.ntfs-3g. I do no see any of those two. I use busybox. Mar 30 19:30:25 Any ideas what is wrong? Thank you. Mar 30 19:32:36 I don't understand why the file 'modules.dep' is not properly populated with all the modules name :| what step am I missing ? anyone has info I can read about it ? thank you ! Mar 30 19:33:01 Im building a custom kernel from my own recipe Mar 30 19:46:14 Casper_: how are the packages being included in your image? Mar 30 19:46:43 did you make a custom image recipe/append? Mar 30 19:49:03 nerdboy: I've created a meta-myserver layer (conf: http://pastebin.com/ndz9AN6q), copiet the recipe from meta-oe/meta-filesystems and added IMAGE_INSTALL_append = " ntfs-3g-ntfsprogs" Mar 30 19:49:48 And of course I appended meta-myserver to BBLAYERS in bblayers.conf Mar 30 19:50:41 i followed the same procedure for including vsftp and that worked (the server is installed and running on my target) Mar 30 19:51:49 copied which recipe and added install append where exactly? Mar 30 19:53:02 * nerdboy would probably append image recipe or maybe just add the IMAGE_INSTALL_append to local.conf and not copy anything Mar 30 19:53:02 I copied the ntfs-3g-ntfsprogs_2013.1.13.bb recipe into my custom layer (the meta-myserver). The IMAGE_INSTALL_append is in my build directory's local.conf. Mar 30 19:53:44 why do you need the recipe copy then? Mar 30 19:54:13 I tried including the meta-oe and just appending but recipe parsing didn't go through. Some Bluetooth stuff is missing. So I just created my own layer. Mar 30 19:54:26 i would just add the layer where it lives Mar 30 19:55:44 Tried that but as I said, the recipes did not parse. Some bluetooth error. My first workaround was to just take what I need so I ceated my own layer (that was when installing vsftp). since it worked, I never went around looking into what is wrong with the meta-oe Mar 30 19:56:51 I now tried the same for ntfs-3d and while it appears to compile OK (looking at the log), the created file system does not contain the ntfs-3d Mar 30 19:57:10 are the packages there? Mar 30 19:57:47 Which packages? The ntfs-3d? In meta-oe? Yes Mar 30 19:58:25 the packages built in your deploy ipk/rpm/deb dir Mar 30 19:58:51 and you should only need to add meta-openembedded/meta-filesystems not the whole thing Mar 30 20:00:14 Packages appear to be there yes. ntfs-3g-ntfsprogs_2013.1.13-r0_cortexa8hf-vfp-neon.ipk in tmp/deploy/ipk/cortexa8hf-vfp-neon for example. Mar 30 20:00:54 I will try ading what you said. Mar 30 20:05:36 ERROR: Layer 'filesystems-layer' depends on layer 'openembedded-layer', but this layer is not enabled in your configuration Mar 30 20:06:32 So just including meta-filesystems does not seem to work. Mar 30 20:09:29 nerdboy: Adding meta-oe as well results in the mentioned Bluetooth error: Mar 30 20:09:31 ERROR: ParseError at /opt/Yocto/poky-dizzy-12.0.1/meta-oe/meta-oe/recipes-navigation/gpsd/gpsd_3.10.bb:23: Could not inherit file classes/bluetooth.bbclass Mar 30 20:09:57 I guess I will have to hunt down this error then. Thanks for now. I'll repor back if there is anything interesting to report. :) Mar 30 20:10:46 the image_install_append thing should work Mar 30 20:13:06 as long as you use package and/or packagegroup names anyway Mar 30 20:13:21 I agree. But the Bluetooth error is thrown whether appending anything or not. It appears to be a corrupt meta-oe layer and bitbake does not find all required classes. As if they were missing. Mar 30 20:13:55 the bluetooth.bbclass for example Mar 30 20:14:06 Do you perhaps have this class anywhere within meta-oe? Mar 30 20:15:01 you're not using poky? Mar 30 20:15:07 poky-std/meta/classes/bluetooth.bbclass Mar 30 20:15:32 * nerdboy currently on master branch Mar 30 20:17:59 Not really sure. I am fairly new at this. The DISTRO variable is set to poky. And everything I downloaded is within a poky-dizzy-12.0.1folder. But I do not see the directory structure you wrote down. Mar 30 20:43:18 poky-std is my non-modified poky build dir Mar 30 20:43:38 below that should look like poky on master branch Mar 30 20:44:21 nerdboy: It seems poky-dizzy-12.0.1 tar I downloaded from Yocto's site does not have the Bluetooth.bbclass. However the master branch does have it. I'll try with that. Tomorrow, though. Time for bed. Thanks for today. Have a nice one! Mar 30 20:45:26 nighty night... Mar 30 21:39:51 In local.conf I did IMAGE_INSTALL_append = " eglibc-staticdev ", but when I build the image I get "ERROR: eglibc-staticdev not found in the base feeds" Mar 30 21:39:58 Is this working for anyone else? Mar 30 21:40:34 * gabrbedd also tried libc-staticdev, libc6-staticdev, etc. They have different, but similar errors. Mar 30 21:41:04 The name you use in IMAGE_INSTALL must match the -package- name as it's know to bitbake. Mar 30 21:41:16 The easiest way to do that is simply to inspect 'PACKAGES = ' in a recipe.. Mar 30 21:41:37 bitbake -e glibc ... then look for 'PACKAGES = ' Mar 30 21:43:00 (from YP 1.7) Mar 30 21:43:00 PACKAGES="glibc-dbg catchsegv sln nscd ldd tzcode glibc-utils glibc-thread-db glibc-pic libcidn libmemusage libsegfault glibc-pcprofile libsotruss glibc glibc-extra-nss glibc-dev glibc-staticdev glibc-doc" Mar 30 21:43:14 so "glibc-staticdev" is the one that matches there Mar 30 21:44:36 * gabrbedd tries that..." Mar 30 21:48:20 Looks like that worked. Error messages are misleading. E.g. if you do libc6-staticdev it'll say something like "nothing RPROVIDES..." Mar 30 21:48:40 ...so you get something that actually is in an RPROVIDES... and it's still not happy. Mar 30 21:49:09 fray: thanks! Mar 30 21:49:23 the RPROVIDES, etc is all automatically generated.. the IMAGE_INSTALL is resolved by looking at the packages availabel to the system.. Mar 30 21:49:36 'package' being the bitbake notion of a package.. it's done this way because the packages can be renamed, etc.. Mar 30 21:52:16 So, RPROVIDES ignores the "provides" in the rpm... and "PACKAGE" ignores the *actual* rpm package name. What you *really* need to do is forget that RPROVIDES exists and use the explicit PACKAGE name (which seems to have changed for the last 3 releases). Mar 30 21:52:31 Yocto 1.7 is awesome... but this one part is still nuts. Mar 30 21:52:33 Mar 30 21:52:35 :-) Mar 31 00:54:21 Hello, I have quick question. I know you can add .bbappend recipe to a .bb pkg recipe. But if I want to modify a .bbclass file, and keep the yocto distro files untouched, can I make a .bbclassappend file? Mar 31 00:58:42 darknighte: 3 verses and a chorus so far Mar 31 00:58:51 well, almost 3... Mar 31 01:05:00 nerdboy: heh. that's good progress. I look forward to hearing it. Mar 31 02:04:52 anyone gets this kind of "warning" while building anything larger than core-image-base? Mar 31 02:05:07 log_check: warning: group $USER does not exist - using root Mar 31 02:05:16 where $USER is my username Mar 31 02:12:39 http://www.gentoogeek.org/files/yocto_reference_blues.txt <= darknighte Mar 31 02:13:14 organic first draft... nothing on terminology yet Mar 31 02:14:36 https://www.youtube.com/watch?v=P0JsmXJoNcc Mar 31 02:15:57 https://www.youtube.com/watch?v=b32JbHowqpQ slightly slicker version Mar 31 02:26:36 chankit2, are you adding a user in your recipe and not setting its groupId? Mar 31 02:28:23 redengin: not at all Mar 31 02:28:44 I was just simply bitbake core-image-sato-sdk Mar 31 02:35:15 and all images but core-image-minimal kernel panic Mar 31 02:40:52 chankit2, are you booting with qemu or real hardware? Mar 31 02:47:31 virtualbox which is a VM Mar 31 02:54:06 are you using the qemu machine type? Mar 31 02:59:09 nope Mar 31 02:59:14 genericx86-64 **** ENDING LOGGING AT Tue Mar 31 02:59:59 2015