**** BEGIN LOGGING AT Mon Dec 15 02:59:59 2014 Dec 15 08:58:27 <_valle_> Good morning! Dec 15 09:05:27 How can I print TUNE_FEATURES varibale from inside recipe file? Dec 15 09:30:40 morning all Dec 15 09:31:25 anyone around? Dec 15 09:31:46 <_valle_> bluelightning: morning! Dec 15 09:41:01 <_valle_> ramose__: You could access it in a recipe build task with ${TUNE_FEATURES} Dec 15 09:42:01 _valle_ Do I need to place it in specific a function? Dec 15 09:42:48 <_valle_> ramose__: You could place it in any of these for example, http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#normal-recipe-build-tasks Dec 15 09:47:17 _valle_: I tried doing it but did not see any value printed,http://pastebin.com/xdSJNekn Dec 15 09:49:13 <_valle_> ramose__: Try outputing it to a file, echo "${TUNE_FEATURES}" > ~/test.txt Dec 15 09:50:28 Hi all. I just bought an Intel Galileo which uses Yocto. I have experience using Raspberry Pi. Can I get Galileo to install new apps using commands like "apt-get install XXX" like Raspberry Pi? If not, do I have to recompile the Yocto image? Dec 15 09:52:37 teachme: there are repositories where you can install packages with "opkg install ..." Dec 15 09:53:19 teachme: here's one guide: http://alextgalileo.altervista.org/package-repo-configuration-instructions.html Dec 15 09:55:54 bluelightning: thanks a lot. Suppose the particular package in opkg is not available. What do I do? Do I compile the binary from source code in Yocto to generate a new image? Or are there easier ways? Dec 15 09:56:05 _valle_:Still no luck,need the value of TUNE_FEATURES for some comparison operation Dec 15 10:00:30 teachme: if the package is not available, yes you will need to build at least the package from source and then make it available in a repo to install onto the existing image Dec 15 10:00:56 teachme: (or copy over the package to the device and install it, but then you need to do the same for any dependencies) Dec 15 10:03:35 bluelightning: when you say copy, you mean cross-compiling the binary on a PC first, then copy the image over either using FTP or using some file manager. Is my understanding correct? It seems like copying is much easier Dec 15 10:04:59 <_valle_> ramose__: http://pastebin.com/40169KVy Dec 15 10:05:01 teachme: yes Dec 15 10:05:16 teachme: right, for one or two packages yes that is easier Dec 15 10:06:25 bluelightning: Thanks. You are most helpful. Is it advisable to test the new binary over QEMU first before transferring to SDcard? Dec 15 10:06:44 teachme: that shouldn't be necessary, no Dec 15 10:07:21 bluelightning: may I ask when would making the new software in a repo be more appropriate compared to copying over the binaries and dependencies? Dec 15 10:07:49 bluelightning: for example, if there are many dependencies, would making it available in a repo be better? Dec 15 10:07:55 <_valle_> I'm running a IMAGE_POSTPROCESS_COMMAND and would like to retrieve some files from a meta-layer. Is this possible? Dec 15 10:07:56 teachme: when the number of dependencies gets large, it becomes tedious to install them all manually yes Dec 15 10:08:21 _valle_: when you start to do that you should consider whether packaging up those files would be a better approach Dec 15 10:08:29 _valle_:Didn't work :( Dec 15 10:09:18 bluelightning: would you have any links on how to make a repo? I have never done that before. Actually, I don't even know what exactly is a repo. Dec 15 10:10:52 teachme: I don't have a guide on that part necessarily, but there is a section of our manual that deals with the build system side of it: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Dec 15 10:10:58 <_valle_> ramose__: If you echo something more, like echo "Something ${TUNE_FEATURES} more" | wall do you see any output? Dec 15 10:12:57 <_valle_> bluelightning: I want to make an upgrade package with some files from the deploy folder and some other files from the meta-layer which isn't in the rootfs. Is packaging up those files the best approach for doing this? Dec 15 10:13:47 _valle_: an upgrade package, what does that mean? Dec 15 10:14:11 bluelightning: thanks. You have been most helpful. Not so scared of Yocto and Galileo now. But I wish it could be easier than Raspberry Pi. Dec 15 10:14:46 teachme: you're welcome. FWIW, we are working to improve things so that there is a wider range of packages available out of the box Dec 15 10:15:03 (we, being Intel, as opposed to the Yocto Project) Dec 15 10:15:29 <_valle_> bluelightning: I just want to make a tarball of some files from the deploy folder, and some files in a meta-layer. However those files in the meta-layer shouldn't be included in the rootfs. What would be the best approach do you think? Dec 15 10:15:38 Going off now. Goodbye. Will probably come back to trouble you folks with more questions later:) Dec 15 10:16:09 bluelightning: I see. With Intel behind, I have even more confidence. Thanks! Dec 15 10:16:11 Bye Dec 15 10:16:38 teachme: cya Dec 15 10:17:07 _valle_: where should the tarball go after it is created? Dec 15 10:17:26 <_valle_> To the deploy folder Dec 15 10:20:59 <_valle_> bluelightning: Could you use SRC_URI in some way in the recipe I use for building the Image to include those files? Dec 15 10:21:29 _valle_: in that case I would suggest using a separate recipe that is depended upon by the image using EXTRA_IMAGEDEPENDS Dec 15 10:22:19 _valle_: yes you can but with an image recipe, do_fetch and do_unpack are disabled and re-enabling them isn't exactly trivial Dec 15 10:22:47 <_valle_> bluelightning: Okay I will try the EXTRA_IMAGEDEPENDS approach, thank you Dec 15 10:51:01 <_valle_> bluelightning: The EXTRA_IMAGEDEPENDS got me the files I needed to the work directory, so far so good. Dec 15 10:51:22 <_valle_> bluelightning: Now I just need to figure out how to get them to the correct folder... Dec 15 10:52:12 <_valle_> bluelightning: Is there any variable to get the current building Image folder? Dec 15 10:52:59 _valle_: within the image recipe ${IMAGE_ROOTFS}, outside of it no Dec 15 10:54:27 <_valle_> bluelightning: Okay, I need it outside unfortunately. Dec 15 11:00:55 that means that what you are doing isn't outside of the image as you were suggesting earlier... Dec 15 11:03:44 <_valle_> Hmm, its that the do_fetch and do_unpack are disabled that gives me a problem. Dec 15 11:04:19 <_valle_> I guess I have to do some workaround for now using the EXTRA_IMAGEDEPENDS and copy the files with a relative path Dec 15 11:06:35 <_valle_> But I don't want the files to ${IMAGE_ROOTFS} but to the folder above so I can work with them Dec 15 11:08:28 I think you are going to be better off doing this in the image recipe if you are touching anything under the workdir of the image (which it seems like you are) Dec 15 11:10:22 <_valle_> bluelightning: Yes that's what I'm doing. However I need some files from the meta-layer to the workdir of the image. And since do_fetch and do_unpack are disabled I got stuck Dec 15 11:12:35 I don't recall what you need to do to re-enable those; you might be able to use an anonymous python function to do d.setVarFlag('do_fetch', 'noexec', None) etc. Dec 15 11:14:50 <_valle_> bluelightning: Thank you for the help. Atleast I got a workaround :). Will investigate how to re-enable those Dec 15 13:14:21 Hi, I am trying to setup eclipse with the yocto plug-in for "Build system derived toolchain", but when I try to reconfiguring the helloworld C Autotools example project, I get the following "Problems": Dec 15 13:14:26 Infos (3 items) Dec 15 13:14:26 Missing PROG arm-poky-linux-gnueabi-dll Dec 15 13:14:26 Missing PROG arm-poky-linux-gnueabi-mt Dec 15 13:14:26 Missing PROG dlltool Dec 15 13:15:13 When I try to build (compile it), I don't get any output in the "Console" window Dec 15 13:17:20 I expect something in the Console window when compiling it, according to what the manual says "To build the project, select Project -> Build Project. The console should update and you can note the cross-compiler you are using." Dec 15 13:23:57 Any ideas? Dec 15 13:32:41 bluelightning: hi Dec 15 13:33:05 hi stiandre Dec 15 13:33:29 stiandre: do you have any clue about my issue? Dec 15 13:33:29 sorry, I don't really know much about the Eclipse plugin Dec 15 13:34:30 bluelightning: ok, but do you have any recommendation on how I can debug my user space application remotely using a good debugger? Dec 15 13:35:11 gdb supports remote debugging with gdbserver, but I've not really used it either I Dec 15 13:35:14 I'm afraid Dec 15 13:35:21 Using a visual debugger (not the gdb commandline) Dec 15 13:35:42 stiandre: I've used qtcreator + GDB-server Dec 15 13:35:42 bluelightning: okay, np :) Dec 15 13:37:23 erbo: that's a possibility, easy to setup? Dec 15 13:42:32 stiandre: I don't think I ran in to much trouble when I tried it, but I have no step-by-step instructions Dec 15 13:42:51 stiandre: okay, thanks Dec 15 14:53:50 Hi there Dec 15 14:54:17 I can't get a working patch for hostapd, and I don't understand what I am doing wrong... Dec 15 14:55:09 Here is the error, and the patch below : http://pastebin.com/5Gh3v6mK Dec 15 14:55:17 if you see something obvious... :p Dec 15 14:59:51 jmleo: perhaps the patch is referencing files one directory too deep? Dec 15 15:00:07 jmleo: patches are effectively applied with -p1 by default Dec 15 15:00:16 which means one directory level will be stripped off Dec 15 15:01:09 so the paths referenced by the patch should probably be e.g. a/src/drivers/drivers.mak rather than a/hostapd-2.2/src/drivers/drivers.mak Dec 15 15:02:46 bluelightning: I tried, but I have the same error Dec 15 15:03:11 ls tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/hostapd/2.2-r0/ Dec 15 15:03:12 0001-hostapd-Don-t-include-libnl-include-directory.patch defconfig hostapd-2.2 hostapd.conf hostapd.service init temp Dec 15 15:03:31 so, the patch should be applied with hostapd-2.2 Dec 15 15:03:49 it'll be applied *within* that directory with -p1 Dec 15 15:06:00 bluelightning: http://pastebin.com/xqSg06dn Dec 15 15:06:04 same error Dec 15 15:06:39 ok, I think I know why Dec 15 15:06:40 what is S set to in the recipe? Dec 15 15:06:50 yes, exactly what I was about to tell Dec 15 15:06:55 S = "${WORKDIR}/hostapd-${PV}/hostapd" Dec 15 15:07:59 ok, I think you may need to add this to the end of the SRC_URI entry for the patch: ;patchdir=.. Dec 15 15:09:48 ok, it works Dec 15 15:10:34 thx bluelightning Dec 15 15:10:53 I will send a patch for oe now if you want ? Dec 15 15:20:09 jmleo: please do yes Dec 15 15:20:27 bluelightning: done Dec 15 15:20:39 I hope I did it well :D Dec 15 15:30:27 I have a local kernel source tree, and I want it to be build using my own meta. It works, but currently, I have to push it and modify the rev in order to build and test it. I read there is a way to have a source directory different from the build directory (I don't want to have the object files in the source tree) but I can't have it working... Dec 15 15:30:39 I have a local kernel source tree, and I want it to be build using my own meta. It works, but currently, I have to push it and modify the rev in order to build and test it. I read there is a way to have a source directory different from the build directory (I don't want to have the object files in the source tree) but I can't have it working... Dec 15 15:30:55 sorry for double posting, bad manipulation Dec 15 15:32:11 are you using a linux-yocto derived kernel recipe? Dec 15 15:32:36 I am using a freescale derived recipe, but I can write a new one Dec 15 15:35:50 jmleo: if this is just for local development, you may be able to use externalsrc: http://www.yoctoproject.org/docs/1.7/dev-manual/dev-manual.html#building-software-from-an-external-source Dec 15 15:36:21 I tried, but it failed (can't remember the error). Will try again and let you informed Dec 15 15:46:04 bluelightning: "ERROR: ExpansionError during parsing /run/media/jm/SSD_JM/Projets/vodabox3/poky/meta-vodalys-bsp/recipes-kernel/linux/linux-vodalys_git.bb: Failure expanding variable WORKDIR: ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: SRCREV was used yet no valid SCM was found in SRC_URI" Dec 15 15:46:42 jmleo: right you will have to clear out SRCREV for the recipe as well when using externalsrc Dec 15 15:47:11 " ExpansionError during parsing /run/media/jm/SSD_JM/Projets/vodabox3/poky/meta-vodalys-bsp/recipes-kernel/linux/linux-vodalys_git.bb: Failure expanding variable WORKDIR: ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: SRCREV was used yet no valid SCM was found in SRC_URI" Dec 15 15:47:13 :) Dec 15 15:47:51 oh right sorry Dec 15 15:48:01 I meant don't use SRCPV in PV Dec 15 15:48:07 when using externalsrc Dec 15 15:48:50 yes, I removed it Dec 15 15:48:55 ok, seems better Dec 15 15:51:25 bluelightning: but the EXTERNALSRC_BUILD will be set too, and I will have my objects in my source tree ? Dec 15 15:51:57 jmleo: are you setting EXTERNALSRC_BUILD ? Dec 15 15:52:07 no Dec 15 15:52:31 ok, in that case no, EXTERNALSRC_BUILD points to a directory under the workdir i.e. separate from the source Dec 15 15:52:45 (by default) Dec 15 16:02:42 bluelightning: Here is the error I had : http://pastebin.com/VXL2myjT Dec 15 16:42:14 jmleo: can you please check, does your kernel recipe inherit kernel-yocto or require linux-yocto.inc ? Dec 15 16:52:12 <_valle_> How do I override the u-boot that is build? I would like to build u-boot v2014.10 instead of u-boot-fslc Dec 15 16:55:44 <_valle_> I tried setting PREFERRED_PROVIDER_u-boot ??= "u-boot" and PREFERRED_PROVIDER_virtual/bootloader ??= "u-boot" with no success Dec 15 16:58:59 _valle_: well, ??= isn't going to override a setting set elsewhere, which I would have to assume it is Dec 15 17:07:27 <_valle_> bluelightning: Thank you Dec 15 17:10:29 <_valle_> bluelightning: To get the v2014.10 branch instead of the master. Should I bbappend the u-boot_2013.07.bb and override the SRC_URI or checkout the other branch? Dec 15 17:17:54 _valle_: bit tricky, you can replace the provided u-boot recipe with your own. Make your new u-boot recipe and place that somewhere in your local meta tree (e.g. machine/meta/recipes-XXXX). Then, edit the conf/bblayers.conf to make the local recipe the first that is scanned (e.g. ${HOME}/Projects/CPU8/Daisy/awsom_dimm/meta-awsom ). Once bitbake is able to satisfy the requirement by the u-boot recipe in your local tree, it will not look Dec 15 17:17:54 into the other bb recipe trees (e.g. meta-yocto, etc.). Dec 15 17:19:49 _valle_: my point was you should use = and not ??= Dec 15 17:20:09 Has anybody used yocto to build minimal base images for docker? Dec 15 17:20:25 <_valle_> bluelightning: Yes I got that and that solved the problem with building the mainline u-boot instead of the u-boot-fslc Dec 15 17:20:51 <_valle_> bluelightning: However that builds the u-boot v2013.07 Dec 15 17:21:04 <_valle_> bluelightning: And I want to build 2014.10 Dec 15 17:21:15 _valle_: is there a recipe for 2014.10 in your configuration? Dec 15 17:21:30 <_valle_> bluelightning: Nope Dec 15 17:21:38 _valle_: ok, you will need to add one Dec 15 17:21:59 I believe patches were sent to add one to OE-Core recently, I don't know if they made it in or not Dec 15 17:23:46 * armpit is asleep behind the wheel again Dec 15 17:43:34 <_valle_> Thank you T0mW and bluelightning. Finally got the u-boot v2014.10 built Dec 15 21:12:17 Has anyone had issues with accessing sourceforge tarballs today? Dec 15 21:12:31 I've been running into issues downloading the lame_3.99.5.tar.gz for some reason Dec 15 21:14:05 Specifically getting this error during a bitbake: Dec 15 21:14:31 ERROR: Fetcher failure: Fetch command failed with exit code 4, output: Dec 15 21:14:36 Read error (Connection reset by peer) in headers. Dec 15 21:14:36 Read error (Connection reset by peer) in headers. Dec 15 21:14:53 ERROR: Function failed: Fetcher failure for URL: 'http://downloads.sourceforge.net/lame/lame-3.99.5.tar.gz'. Unable to fetch URL from any source. **** ENDING LOGGING AT Tue Dec 16 02:59:58 2014