**** BEGIN LOGGING AT Mon Feb 09 02:59:58 2015 Feb 09 08:33:59 good morning Feb 09 09:12:11 Hi Feb 09 09:53:27 morning all Feb 09 10:10:07 bluelightning: good morning .. Feb 09 10:10:13 hi maxin Feb 09 10:11:06 bluelightning: hi, I got a segfault with bitbake and reported it: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7299 Feb 09 10:11:09 Bug 7299: critical, Undecided, ---, richard.purdie, NEW , "bitbake -g -u depexp " segfaults and hogs memory while connecting to server through ssh Feb 09 10:20:41 maxin: ok, thanks Feb 09 11:34:53 Hi every one, can I associate a global variable to an user with YOCTO (with useradd.bb for example?) I would like to export TZ=Europe/Paris? Feb 09 11:37:13 Where can I find out which versions of the beagleboard a Yocto-release has been tested on? Feb 09 11:38:09 ah. found it. Feb 09 11:40:10 TuTizz: I would say you have to provie a .profile for that user Feb 09 11:40:16 provide Feb 09 13:16:53 abelloni, ok, I will try that way. Feb 09 13:55:50 bluelightning: hi, when I run populate_sdk task for one of my images, I get an error regarding multiple provides for libgcc. this doesn't happen when I build the same image for my cross target Feb 09 13:58:24 bluelightning: I can see that it is trying to build libgcc_4.9.bb becaue the following line in meta/conf/distro/include/default-providers.inc: PREFERRED_PROVIDER_libgcc ?= "libgcc" Feb 09 14:00:28 bluelightning: meta-sourcery layer adds the following: PREFERRED_PROVIDER_libgcc = "external-sourcery-toolchain" so it should override the defautl setting - right? Feb 09 14:02:54 bluelightning: but then nativesdk-libgcc still points to the libgcc_4.9.bb recipe.....can you see what's going on? i would have thought that the nativesdk-libgcc could be different Feb 09 14:03:38 darkhorse_: can you please (a) pastebin the error and (b) check bitbake -e | grep ^PREFERRED_PROVIDER.*libgcc Feb 09 14:15:18 bluelightning: done - http://pastebin.com/m92U6Jb9 Feb 09 14:22:21 darkhorse_: this is really a question for someone who maintains/uses meta-sourcery but maybe what is needed is: PREFERRED_PROVIDER_nativesdk-libgcc="external-sourcery-toolchain" Feb 09 14:33:12 Hi ! Since this morning I've got an error while compiling linux-yocto : it complains it can't find some .path files while doing do_patch(). FYI I use kernel 3.14 + preempt-rt for a beaglebone Feb 09 14:33:22 Here is the complete log : http://pastebin.com/9HKuYXeS Feb 09 14:35:04 I guess it has something to do with the latest update to v.3.14.29 Feb 09 14:35:36 But I really don't know where to start to solve this :( Feb 09 14:38:50 bluelightning: thanks - i will try this Feb 09 14:40:31 zeddii: ^ Feb 09 14:57:50 bluelightning: a more general question: i want to provide basically the contents of the tmp/sysroots/ to the application developers. is "bitbake -c populate_sdk" the correct way to do it? If yes, why is it trying to build native version of everything Feb 09 14:58:23 darkhorse_: yes; and that's not quite what it's doing Feb 09 14:59:00 darkhorse_: when you see "nativesdk" there, that is building an SDK that is capable of running on a third system (specified by SDKMACHINE, defaults to the same as your current system) Feb 09 14:59:37 darkhorse_: this means for example you can build an SDK for 32-bit x86 on an 64-bit system Feb 09 15:00:36 bluelightning: oh - do you think I need to set SDK machine to be the same as my target then? I don't want to build a native SDK for now Feb 09 15:01:51 darkhorse_: no, SDKMACHINE is the machine which the SDK is intended to run _on_ not the machine it's intended to build for - the latter is still MACHINE Feb 09 15:03:56 bluelightning: i understand that. but my target is to provide thinkgs linke kernel headers and other package headers + the static libraries for other teams to link against when they are building for the cross target....it seems SDKs are not meant for that purpose Feb 09 15:05:09 bluelightning: it seems more like that I should simply provide the tmp/sysroots/ directory instead because it already contains everthing they need Feb 09 15:06:19 not sure why you think sdks aren't made for that purpose. the sdk contains two sysroots, one for the machien ti runs on, one for hte target, and both can have extra packages added to it Feb 09 15:08:03 kergoth: alright. this is what I was trying to understand ( am generating SDK for the first time). thanks Feb 09 15:08:44 see TOOLCHAIN_HOST_TASK and TOOLCHAIN_TARGET_TASK in populate_sdk_base.bbclass Feb 09 15:08:46 kergoth: I am still having trouble with meta-sourcery trying to use it with cross-ng toolchain. http://pastebin.com/m92U6Jb9 Feb 09 15:09:16 kergoth: bluelightning suggested PREFERRED_PROVIDER_nativesdk-libgcc="external-sourcery-toolchain" but that didn't help either :( Feb 09 15:09:46 most likely one of the packages in libgcc isn't in external-sourcery-toolchain Feb 09 15:10:18 check PACKAGES in each Feb 09 16:33:41 TPTM: hi Feb 09 16:33:53 oh! :) Feb 09 19:43:19 good morning Feb 09 20:09:51 does anyone here understand how to generate core dumps with busybox? Feb 09 20:10:07 http://elinux.org/images/0/0c/Elc2013_Lelong.pdf -> Page 16 seems to explain the process, but it is a bit confusing to me. Feb 09 20:13:04 hmm, I think I am getting it! Feb 09 20:49:43 lpapp: The kernel generates core dumps. As far as I can tell, that busybox option just causes the busybox init to call setrlimit() for child processes. Feb 09 21:48:03 Hi all Feb 09 21:48:32 i'm beginner Feb 09 21:49:03 and can i ask some questions about recipes dependencies ? Feb 09 21:52:33 i checked out meta-raspberrypi and i can generate an image using bitbake meta-raspberrypi Feb 09 21:52:59 but when i see the recipe i can only see that it includes include recipes-core/images/core-image-minimal.bb Feb 09 21:53:12 not the bsp specific recipes Feb 09 21:53:34 how can it be built ? Feb 09 21:53:36 thanks Feb 09 21:54:16 jojo_: er... bitbake meta-raspberrypi shouldn't work Feb 09 21:54:24 are you sure that's what you're running? Feb 09 21:55:43 no sorry tipo error Feb 09 21:56:12 i'm folowing Feb 09 21:56:13 https://delog.wordpress.com/2014/09/16/embedded-linux-system-for-raspberry-pi-with-yocto-project/ Feb 09 21:56:24 bitbake rpi-hwup-image Feb 09 21:56:35 when i open rpi-hwup-image Feb 09 21:57:13 it is set this : include recipes-core/images/core-image-minimal.bb Feb 09 21:57:43 yes, and that's not a problem - it just means it's based on core-image-minimal Feb 09 22:00:00 can you explain the problem you're trying to solve? Feb 09 22:00:33 how are loaded raspbery specific recipes Feb 09 22:01:06 oups i think i found Feb 09 22:01:16 it loads BBFILES Feb 09 22:01:38 in meta-raspberrypi/conf/layer.conf Feb 09 22:02:27 but what is the difference between meta-raspberrypi/conf/layer.conf and include recipes-core/images/core-image-minimal.bb Feb 09 22:03:03 meta-raspberrypi/conf/layer.conf is brought in when you add the meta-raspberrypi directory to your bblayers.conf Feb 09 22:03:27 the "include" statement basically just says include the contents of the named file at this point in the current file Feb 09 22:04:02 then no doubt the rpi-hwup-image recipe makes some customisations after that Feb 09 22:05:27 but this is two different ways to tell the same thing : include recipes ? Feb 09 22:05:44 no, these are two very much unconnected things Feb 09 22:07:01 each layer's layer.conf extends BBFILES so that the layer's recipes are made available for bitbake to read, that is correct Feb 09 22:07:38 the "include" statement on the other hand is just a way to include the contents of another single file within the context of the file the include statement appears in Feb 09 22:08:28 i.e. a way to say "this recipe is the same as this other recipe, except for some differences which I have specified after the include statement" Feb 09 22:08:33 does that make sense? Feb 09 22:09:33 ok but what i'm not understanding is that for example in BBFILES ok specific recipes are made avalable to read Feb 09 22:09:44 but when are they called Feb 09 22:10:14 depends what you mean by "called" Feb 09 22:10:28 included Feb 09 22:10:31 i mean Feb 09 22:10:58 when you run bitbake rpi-hwup-image you are asking to build a recipe that is part of meta-raspberrypi - without that layer, that command would fail Feb 09 22:11:34 actually, this page is missing an important step AFAICT Feb 09 22:11:49 you need to also set MACHINE = "raspberrypi" I think Feb 09 22:12:05 (in conf/local.conf under your build directory) Feb 09 22:12:30 when i call bitbake rpi-hwup-image it includes directly "include recipes-core/images/core-image-minimal.bb" Feb 09 22:12:40 which is outside this bsp Feb 09 22:13:18 my understanding is that it bypass specific bsp recipes Feb 09 22:13:39 that's not how I would describe it Feb 09 22:14:02 the include statement will cause bitbake to search BBPATH for recipes-core/images/core-image-minimal.bb Feb 09 22:14:13 BBPATH is also extended by each layer's layer.conf Feb 09 22:14:20 it will find that file in the meta/ subdirectory Feb 09 22:15:11 ok Feb 09 22:15:22 thanks for you help Feb 09 22:15:31 i think i understood Feb 09 22:20:12 jojo_: ok, but definitely check what MACHINE is set to in your conf/local.conf Feb 09 22:22:52 ok thanks Feb 09 22:23:05 also folowed https://wiki.yoctoproject.org/wiki/How_do_I Feb 09 22:23:13 it helped to understand Feb 09 22:23:17 thanks a lot Feb 09 23:36:09 Hey all, does anyone know how to include all results of a recipe into an image? Feb 09 23:36:42 I am building the erlang package, and there is alot of erlang-* files that are produced, and I would like to just add all of them Feb 09 23:41:32 Matulis: As far as I know there is no way to say, "Install all packages from this recipe" Feb 09 23:41:49 is there a good way to get a list of what packages are built? Feb 09 23:42:06 Matulis: That should be in the PACKAGES variable for the recipe Feb 09 23:44:11 so this erlang recipe produces a bunch, and it looks to not have a PACKAGES variable Feb 09 23:45:04 Matulis: It has one, if it isn't changed it the recipe it just has the default values Feb 09 23:45:44 it looks like there might be a script that generates a manifest.inc Feb 09 23:45:50 https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PACKAGES Feb 09 23:46:01 Where is the recipe from, I could take a look Feb 09 23:46:25 http://layers.openembedded.org/layerindex/recipe/24401/ Feb 09 23:47:23 looks like the python script generates that manifest.inc, and it has a PACKAGES variable, but how can I used the list with the ${PN} substitued? Feb 09 23:47:37 manifest.inc is specific to python only Feb 09 23:47:43 and PN is the name of the recipe Feb 09 23:48:29 so if I was trying to include all the packages of a recipe in my own image, would I just define a PN variable and add the packages list? Feb 09 23:50:36 It looks like the already create a meta package for you in the manifest.inc. Does adding erlang-modules to the image work? Feb 09 23:52:09 See http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services/tree/meta-openstack/recipes-devtools/erlang/erlang-R16B03-1-manifest.inc#n1112 Feb 09 23:52:45 ah awesome!! Feb 09 23:53:08 thank you very much guys, I've been like manually adding parts.. Feb 09 23:53:41 Matulis: I'm not sure that's what you want, I've never looked at the erlang recipe. Feb 09 23:53:50 Matulis: Hopefully it is :) Feb 09 23:54:24 it actually is, i have a package which depends on erlang which I am trying to compile natively, and it keeps failing and I have to iterate and add new packages Feb 09 23:54:34 now I can just add all, and optimize later Feb 09 23:55:19 Ok great! **** BEGIN LOGGING AT Tue Feb 10 01:42:16 2015 **** ENDING LOGGING AT Tue Feb 10 02:59:58 2015