**** BEGIN LOGGING AT Mon Mar 24 02:59:59 2014
Mar 24 04:56:25 hi yocto. I need to add the core-image-minimal-initramfs(at tmp/deploy/images) with kernel image itself by CONFIG_INITRAMFS_SOURCE and i finally want to build a kernel with initramfs.Is it possible?
Mar 24 08:32:24 good morning
Mar 24 09:27:27 good morning
Mar 24 09:38:17 im working with a yocto-based linux distribution. what would be the easiest way for me to provide my own linux kernel config?
Mar 24 09:42:54 morning all
Mar 24 09:43:13 good morning
Mar 24 09:49:05 today i'm using x11-base which is using matchbox, does someone know how to use a better WM than matchbox such as openbox or XFCE ?
Mar 24 09:54:49 better in what sense?
Mar 24 10:28:36 what does it mean to be "Yocto compatible"? For example, the TI Arago project claims to be Yocto 1.4 compatible, but I don't fully understand what Yocto is in this sense? Is it a set of layers? I can only see OE layers in Arago
Mar 24 10:31:20 is it possible to use a different toolchain(than poky) to build a custom kernel for a particular MACHINE ?
Mar 24 10:32:19 mago_: see https://www.yoctoproject.org/ecosystem/yocto-project-compliance-program. there isn't a lot there.. but it gives you the idea.
Mar 24 10:38:33 but does the Yocto project provide/maintain any layers of its own? or is Yocto more of a documentation/standardization project for OpenEmbedded?
Mar 24 10:43:28 mago_: well, the Yocto Project's main activity is maintaining OE-Core and BitBake (with significant help from the wider community)
Mar 24 10:45:21 and Poky is an example distribution based on OE, maintained and supported by Yocto?
Mar 24 10:46:05 mago_: in a sense it's both an example distribution and a reference build system
Mar 24 10:46:34 mago_: the poky repository is OE-Core + BitBake + meta-yocto + meta-yocto-bsp + documentation
Mar 24 10:47:40 oh, so there is a meta-yocto. I just found the yocto linux kernel recipes in my cloned OE-core repo
Mar 24 10:48:04 meta-yocto mostly just contains the poky distro configuration
Mar 24 10:48:34 but you don't absolutely need all of those bits; OE-Core + BitBake is the minimal set
Mar 24 10:53:34 bluelightning: the issue I had was.. libgtp+sgsn are both built as part of the OpenGGSN build (same git repository/recipe)
Mar 24 10:53:47 bluelightning: I bumped the SRCREV again and this time I didn't have issues
Mar 24 10:55:04 zecke: was it seeing libraries within the sysroot rather than in the build dir for the recipe perhaps?
Mar 24 10:55:26 the old libraries, that is
Mar 24 11:00:37 bluelightning: yes, somehow the package code decided that sgsn-emu links against the previously built libgtp and not the one that was build as part of the sgsn
Mar 24 11:01:12 zecke: I can only assume because in the linker command line the sysroot dir came first
Mar 24 11:02:53 bluelightning: yes? I don't know how the solib code is working nowadays but don't we just lookup libgtp.so.0 and find the package that provides that?
Mar 24 11:03:26 bluelightning: so it looks like in my case the order of creating/updating the shlibs and the time the package was created was the wrong way
Mar 24 11:03:46 zecke: that all happens at packaging, after the linking has occurred... if I'm not mistaken the problem started in do_compile
Mar 24 11:04:35 zecke: do you still have the workdir of the recipe from when it was broken?
Mar 24 11:05:13 if not, I guess it shouldn't be too hard to reproduce
Mar 24 11:11:14 bluelightning: I have the recipe but I did the same again. Changed the SRCREV and this time it worked. I think it might be a hard to find race. :(
Mar 24 11:14:18 Hi everyone. I have SRC_URI = "git://github.com/carhartl/jquery-cookie.git;protocol=https" . Shouldn't do_unpack() put sources from ${WORKDIR}/git/ into ${S} ? At the moment ${S} is empty :(
Mar 24 11:17:16 Denwid: no, it's the other way around
Mar 24 11:17:29 Ah I have to set S = "${WORKDIR}/git"
Mar 24 11:17:40 Denwid: S must be set to point to where the sources have been unpacked, i.e. it should be set to ${WORKDIR}/git yes
Mar 24 11:17:48 thanks =)
Mar 24 11:51:47 how to compile msm linux kernel using yocto build system
Mar 24 13:07:22 abc_: afaik, there isn't any recipe for any msm boards yet. so you would need to make your own 'bsp' layer.
Mar 24 13:43:04 is there new name already picked for 1.6?
Mar 24 13:55:30 https://wiki.yoctoproject.org/wiki/Releases 1.6 daisy
Mar 24 14:00:20 daisy, such a lovely name
Mar 24 14:01:21 being a name-picker must be fun
Mar 24 15:15:35 YAB: hello
Mar 24 15:22:57 I used to have 'SRC_URI' in image recipe on dylan - that worked
Mar 24 15:23:11 now after bumping to 1.5 dora - it is simply ignored
Mar 24 15:23:44 so 'do_fetch' doesn't do anything for that image
Mar 24 15:24:06 any ideas?
Mar 24 15:27:45 Xz: were you doing anything else to do_fetch to ensure that executed? do_fetch is marked noexec for image recipes
Mar 24 15:28:24 Xz: really, image recipes aren't supposed to fetch anything, the preferable solution is to do that from another recipe, package the result and then pull the package into the image
Mar 24 15:29:43 bluelightning: d.delVarFlag("do_fetch", "noexec")
Mar 24 15:29:50 bluelightning: I do that in python function
Mar 24 15:30:10 bluelightning: basically it's used for shipping grub.conf alltogether
Mar 24 15:30:32 bluelightning: and grub.conf is image-specific (contains image name)
Mar 24 15:31:04 I see
Mar 24 15:31:06 bluelightning: and the only way to determine image name is from the image recipe
Mar 24 15:31:25 bluelightning: I was breaking my head to do it any other way
Mar 24 15:32:56 ok; well d.delVarFlag("do_fetch", "noexec") in anonymous python should work
Mar 24 15:33:51 python () { # Ensure we run these usually noexec tasks d.delVarFlag("do_fetch", "noexec") d.delVarFlag("do_unpack", "noexec")
Mar 24 15:33:54 }
Mar 24 15:33:58 bad paste
Mar 24 15:34:09 anyway - that's how it looks like in image recipe
Mar 24 15:35:59 Xz: I guess I will have to run a test here
Mar 24 15:37:47 bluelightning: I think I found the problem
Mar 24 15:38:01 hi there !
Mar 24 15:38:06 bluelightning: SRC_URI gets triggered in 'do_unpack' for some reason
Mar 24 15:38:11 bluelightning: instead of 'do_fetch'
Mar 24 15:38:31 and I added task 'after do_fetch before do_build'
Mar 24 15:39:11 Xz: it's not that SRC_URI is "triggered"; copying of local files to ${WORKDIR} might be though
Mar 24 15:39:15 Xz: there has to be a better way to solve this...
Mar 24 15:39:35 I have accidentally removed the rootfs from my deploy directory... And now, when I do a bitbake fsl-image-test it fails with an exception : No such file or directory: 'build/tmp/deploy/images/nitrogen6x/fsl-image-test-nitrogen6x-20140324150700.rootfs.tar.bz2'
Mar 24 15:40:37 jmleo: try bitbake -c clean fsl-image-test first
Mar 24 15:40:40 i tried to do a bitbake -c clean fsl-mage-test and relaunch the bitbake fsl-image-test
Mar 24 15:40:46 and it is not working either
Mar 24 15:41:14 I still have some files in the deploy directory
Mar 24 15:42:12 http://pastebin.com/wmTiepgJ
Mar 24 15:45:48 jmleo: so which task is actually failing?
Mar 24 15:46:34 the do_rootfs
Mar 24 15:49:25 jmleo: can I have a pastebin of the full error please
Mar 24 15:50:58 bluelightning, http://pastebin.com/uQkp33yf
Mar 24 15:51:57 jmleo: ok, I would suggest deleting the broken symlink that points to the image file you deleted
Mar 24 15:52:12 it shouldn't fail this way, but that would be the workaround
Mar 24 15:54:07 bluelightning, yes, it passed (well, the next broken link failed too, but at least, this is an explanation)
Mar 24 15:57:57 I have entered bug 6029 for this
Mar 24 15:57:58 Bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=6029 normal, Undecided, ---, laurentiu.palcu, NEW , Ignore broken symlink when RM_OLD_IMAGE is enabled
Mar 24 16:16:39 thx bluelightning yocti
Mar 24 16:43:24 after bumping to 1.5 linux-kernel tmp dir with modules is empty: packages-split/kernel-modules/
Mar 24 16:43:53 so I cannot do anymore 'IMAGE_INSTALL += "kernel-module-usb-storage"'
Mar 24 16:44:19 moin
Mar 24 16:44:54 there is only ipk with all of them: kernel-modules_3.8-r0.ipk
Mar 24 16:50:06 Xz: does that ipk actually contain anything?
Mar 24 16:50:29 Xz: it sounds to me like the configuration has changed such that there are no modules and thus none are packaged
Mar 24 16:51:42 * nerdboy still has a metric a**load of module ipks from last night's build
Mar 24 16:52:15 is that the default yocto kernel?
Mar 24 16:54:08 bluelightning: ipk has 1024 bytes, so apparently it does not contain modules
Mar 24 16:54:59 nerdboy: it's 1.5 Yocto (dora), linux-yocto kernel 3.8
Mar 24 16:55:09 nerdboy: with set of my patches
Mar 24 20:49:37 * kergoth fights sstate
Mar 24 21:17:25 seriously? you're rebuilding *quilt-native*? *really*?
Mar 24 21:17:54 * kergoth sighs
Mar 24 21:31:54 sometimes i really hate sstate
Mar 24 21:31:57 its a love/hate relationship
**** ENDING LOGGING AT Tue Mar 25 02:59:58 2014