**** BEGIN LOGGING AT Mon Jul 29 03:00:13 2019 Jul 29 07:40:15 good morning Jul 29 07:49:44 good morning! Jul 29 08:00:26 good morning! Jul 29 08:24:38 New news from stackoverflow: RaspberryPi B+ not booting for Yocto Jul 29 08:48:32 l Jul 29 09:15:06 Dear All, Jul 29 09:15:06 I'm trying to modify the TARGET_CPPFLAGS globally. Jul 29 09:15:06 What I see is that those are set to "" in bitbake.conf file and then those can be / are updated in local.conf Jul 29 09:15:06 I'm wondering why those settings are not overrided by distro -> like set this value in distro/foo.conf in my meta-foo ? Jul 29 09:15:42 I can add those modifications to TARGET_CPPFLAGS in local.conf, but it would be more handy to add them to distro Jul 29 09:15:44 hello all Jul 29 09:15:49 Is it possible? Jul 29 09:16:01 here: https://software.intel.com/sites/default/files/managed/f0/52/Using_Intel_System_Studio_with_the_Yocto_Project.pdf they write one can use the TOOLCHAIN variable to specify a certain toochain to be used for buildign a package Jul 29 09:16:15 but I can't find this variable used in poky, neither in the mega-manual Jul 29 09:16:41 they write that simply saying TOOLCHAIN_pn-${PN} = "icc" is enough. how is this possible? Jul 29 09:36:18 looks like this TOOLCHAIN variable is something that intel' Jul 29 09:36:29 it is from them Jul 29 09:37:44 lukma: You can control anything from the distro that you can from local.conf Jul 29 09:47:52 RP: So is it possible to move adjustments from local.conf to meta- stuff ? Jul 29 09:48:19 RP: Otherwise, I need to use e.g. KAS to deploy the OE/Yocto meta layers Jul 29 09:48:36 which will generate local.conf for me at every time Jul 29 09:48:49 (My goal is to have automatic deployment) Jul 29 09:49:15 lukma: not just possible, that is what distro configs are for Jul 29 09:52:04 RP: I may be wrong -> when I add TARGET_CPPFLAGS += "-D _FOO1" to distro (foo.conf) then it is not visible on the whole build Jul 29 09:52:27 but when the same line is added to local.conf I see it modified for every recipe when it is build Jul 29 09:53:13 hence the question can I achieve this with any modification of distro (foo.conf) or any other way in meta-xxx ? Jul 29 09:53:13 Or is it only possible with local.conf ? Jul 29 09:55:24 lukma: read the end of conf/bitbake.conf - you will see that distro config and local.conf are included just after each other Jul 29 09:55:49 lukma: so they both behave the same. Are you setting DISTRO = "foo"? Jul 29 09:56:42 RP: Yes, I do set DISTRO explicitly Jul 29 09:56:51 But, Ok, I will double check this Jul 29 10:11:00 if a recipe include file is shared by several recipes, and you want to put the recipes into their own directories, where should the include file be? Jul 29 10:11:32 is it OK to have a structure as recipes-/{inc,recipe-a, recipe-b} ? and both recipes include things from inc/ ? Jul 29 10:50:36 @lit Jul 29 10:52:54 litb I did that already. There should be no issues. Just note, that your include files are fetched and put into the respective /tmp/work folder for each recipe Jul 29 10:53:35 as long as you do not try in install the common files into your root file system everythign is fine Jul 29 11:55:15 New news from stackoverflow: prelink-rtld: command not found Jul 29 11:56:55 * alessioigor waves all Jul 29 11:56:57 In your opinion is CC-BY-4 license suitable for a layer? Jul 29 11:57:47 alessioigor: if i'm not mistaken this is pretty much the same as MIT, right? Jul 29 11:58:24 (which is the de-facto standard for layers) Jul 29 11:59:00 LetoThe2nd: It should be but I don Jul 29 11:59:05 't know it very well Jul 29 11:59:47 alessioigor: i'd say just stick to MIT, unless you have a good reason to not do so. Jul 29 12:01:05 LetoThe2nd: Ok thanks! Jul 29 12:10:52 alessioigor: CC is typically for documents Jul 29 12:11:28 alessioigor: I usually use MIT or GPLv2 for software Jul 29 12:13:13 mckoan: That is interesting: Are Yocto recipes more like documents or more like software? Jul 29 12:13:49 hmm, more like they document how the software is built Jul 29 12:13:56 in a machine readable form Jul 29 12:14:57 Crofton|work: even a C source is documenting what to execute in a machine readable form though. Jul 29 12:35:04 how can I specify a LIC_FILES_CHECKSUM filename with spaces? Jul 29 12:35:32 i tried %20 and "\ " Jul 29 12:36:45 ah.. missed the other space-containing file Jul 29 13:16:54 Hi, if I add the package "kernel-modules" to my yocto, how do I prevent the automatic loading of a certain kernel module? Jul 29 13:18:54 fbre: find out why it is even marked to be autoloaded Jul 29 13:19:13 fbre: AFAIK they usually should not be, unless we're talking about device drivers. Jul 29 13:19:46 yes, it's a device driver Jul 29 13:21:04 fbre: then your buzzword is "odule blacklisting" Jul 29 13:21:29 I see! cool, thanks Jul 29 13:23:39 Hello, i've bitbake 'busybox' and trying to deploy it with opkg (which is enabled) on the target Jul 29 13:23:49 if it is a right way do do so? Jul 29 13:24:01 i mean opkg install busybox.ipk Jul 29 13:24:08 or it is a bad idea? Jul 29 13:24:39 i've tried to do so -- and my rootfs was ruined Jul 29 13:25:07 thx for help Jul 29 13:26:33 Another thing that is failing for me is 'bitbake -c menuconfig busybox' Jul 29 13:26:49 ygeorgie: are you able to ruin your rootfs also by installing a different package via opkg? Jul 29 13:26:50 i've got a segfault Jul 29 13:27:11 no-no... all the rest (the one i've tried) worked... Jul 29 13:27:41 but in general -- if it is a normal practice to do opkg busybox? Jul 29 13:28:10 it should normally work, right? Jul 29 13:29:07 ygeorgie: its a rather uncommon practise, usually people don't even have package management on their targets. Jul 29 13:29:19 i see... Jul 29 13:29:42 how i do deploy a newly build busybox on the target then, what is the correct way? Jul 29 13:30:00 the thing i want to do -- is just to add some more 'goodies' in it... Jul 29 13:30:08 CONFIG_LSUSB=y in my case Jul 29 13:30:15 ygeorgie: its very difficult to build an image *without* busybox Jul 29 13:30:22 hehehe Jul 29 13:30:33 yep... initial image sure with busybox. Jul 29 13:30:40 but a minimal one... Jul 29 13:30:42 ygeorgie: rather rebuild the image, then. Jul 29 13:30:50 i see.... Jul 29 13:30:59 ygeorgie: so just edit the defconfig and rebuild Jul 29 13:31:16 if installing a new busybox doesn't work then please file a bug with the log Jul 29 13:33:07 but it is completely 'legal' todo 'opkg install busybox.ipk' , right? Jul 29 13:34:21 if you've copied enough of the packages to the target, or even better just setup a feed, then ye Jul 29 13:34:22 yes Jul 29 13:34:45 aha... i should have a feed, right? Jul 29 13:34:50 this one i don't Jul 29 13:35:06 i am just wget from my local host Jul 29 13:35:59 i am in the initial HW board bootstrap mode now.. just trying to do some initial tests... Jul 29 13:37:20 sorry for poking you with this (maybe stupid) questions... Jul 29 13:37:39 but it appears i've never deployed busybox.ipk for some reason on the target... Jul 29 13:38:06 ygeorgie: this all happens under the hood in do_rootfs Jul 29 13:38:47 can you elaborate a bit pls... Jul 29 13:41:30 ygeorgie: the do_rootfs step when an image is built is (roughly) this: "take all packages and install them to a directory, then make a blob out of the result" Jul 29 13:41:53 thx Jul 29 13:41:57 ygeorgie: so whenever you build an image, under the hood opkg install is run for every package. Jul 29 13:43:02 unless you are using deb or rpm, of course! Jul 29 13:43:15 no-no... opkg Jul 29 13:44:30 ygeorgie: unless you went to serious effort, you've already got busybox installed Jul 29 13:44:44 what does /bin/sh point to on the target? Jul 29 13:44:47 yep.. it is.. Jul 29 13:44:49 busybox Jul 29 13:45:01 but the problem is that i want to extand it a 'bit' Jul 29 13:45:05 right so just fiddle the defconfig to add what you want, and rebuild the image Jul 29 13:45:22 or if you can replicate opkg failing an upgrade, file a bug with the log Jul 29 13:45:27 oki Jul 29 13:53:11 load_modules=off as uboot kernel parameter is the trick Jul 29 13:54:01 Then no kernel module will be loaded and I can probe certain kernel modules to load them Jul 29 14:55:47 New news from stackoverflow: Yocto Custom Layer run Tune2fs on do_rootfs after mkfs.ext4 Jul 29 15:15:01 RP: Is there a trick to using ABHELPER_JSON in the autobuilder config.py file? I used os.environ to set the variable to both config.json and config-local.json (which is located in the same path) however utils.py isn't picking it up. Jul 29 15:19:17 tgoodwin: which os.environ are you putting that into? You probably have to set the on the controller before you start buildbot Jul 29 15:20:41 tgoodwin: oh, extra_env = {"ABHELPER_JSON" : "config.json /home/pokybuild/config-local.json"} in builders.py maybe? Jul 29 15:21:27 RP: Based on the walkthrough, I was making the os.environ call from config.py. I then tried setting it in the environment of my systemd service (same result, no dice). Jul 29 15:22:40 I had not tried going the extra_env route. Jul 29 15:25:12 That worked better until it got to the "shared repositories" section of the a-quick build. The error indicates that under a-quick's directory (on the worker), the yocto-autobuilder-helper/scripts/../config-loca.json doesn't exist (which it wouldn't since that is a fresh clone of the helper. Jul 29 15:27:09 I suppose the work-around to this is to fork/branch yocto-autobuilder-helper to include one's own extra configuration file(s) if you want the builders to also have access to those changes. Jul 29 15:27:27 (if it's a remote worker, that is). Locally...just use an absolute path. Jul 29 15:51:40 tgoodwin: yes, its not ideal. Happy to take patches to improve some of this btw Jul 29 16:31:40 RP: Sure thing! Once I get this working on my end I'll see what's actually helpful. My current "a-quick" build made it through stage 8 with warnings and all the triggers after it started failing just now. The UI is also locked up so I'm having a hard time tracing it down. Jul 29 16:32:16 Ah... ran out of space. Jul 29 16:55:40 Hi, do you know if it's possible to build a yocto image using GPU and how to do it? I didn't find the answer on google :/ Jul 29 17:14:40 alex3600, can you provide context for the question? Why would you want that? Jul 29 18:07:13 hi, i was working on a multiconfig build and i was invoking the build with the following command "bitbake multiconfig:: multiconfig::" and it was working fine. I continued to work on the project recently but the command failed with the error "ERROR: Nothing PROVIDES 'multiconfig::". Did anything change the way Jul 29 18:07:13 multiconfigs work? Thanks in advance Jul 29 18:08:11 ssajal: Are you using a recent commit from master? Jul 29 18:09:16 Also, I think "multiconfig" was renamed to "mc".... try "mc::" Jul 29 18:10:05 kanavin: my computer is not powerful enough to compile with cpu Jul 29 18:10:21 * ssajal trying mc:.... Jul 29 18:28:02 jpew: mc seems to have worked :) Jul 29 18:28:14 thanks a bunch Jul 29 18:46:28 RP:https://pastebin.com/mK7Dvkxw Jul 29 18:52:02 Hi, is it possible to build a yocto image using GPU? :) Jul 29 18:53:23 alex3600: no Jul 29 18:53:30 simple as is :) Jul 29 18:53:56 alex3600: unless you have a gpu that is x86 and running linux, of course. Jul 29 18:54:24 LetoThe2nd> ahah okay Jul 29 18:54:35 LetoThe2nd> yes I have Jul 29 18:55:43 alex3600: i actually doubt that, but if you really have then it should be able to run bitbake :) Jul 29 18:56:54 LetoThe2nd> hum .. I didn't explain very well. I want to build using my geforce gtx 950m :) so my GPU cores Jul 29 18:57:33 alex3600: not possible. it is neither x86, nor is it running linux Jul 29 18:59:39 LetoThe2nd> oh ok, I'm actually able to do that with neuronal networks I thought it was possible with yocto :/ Jul 29 19:01:12 alex3600: completely different world. reason: gpu are optimizing for workloads that are highly parallelizable, like videos, images, or as you said neural networks, machine learning, etc. Jul 29 19:01:53 alex3600: compiling things on the other hand need way fewer tasks, but those are way more complex. thats why you really need a proper cpu. Jul 29 19:02:24 LetoThe2nd> okay, thanks you very much :) Jul 29 19:04:30 RP:if I revert top 4 sstatesig: patches from https://git.openembedded.org/openembedded-core/log/?h=master-next it works again Jul 29 19:50:50 alex3600: if you patch gcc to make it run steps on the gpu then that would be awesome. that's probably a PhD of effort though Jul 29 19:56:56 rburton: I'm working on it don't worry Jul 29 20:26:43 New news from stackoverflow: Yocto Warrior on INITRAMFS_IMAGE_BUNDLE and Linux Kernel Image on SD Card Image Jul 29 21:15:22 rburton: wiith llvm it will happen sooner Jul 29 21:21:52 khem: sorry, those need bitbake master-next Jul 29 21:22:07 khem: just testing out some bigger API changes to see if they're going to make sense **** BEGIN LOGGING AT Mon Jul 29 22:00:46 2019 Jul 29 22:48:05 khem: its going to get worse in -next for a short while btw, I need to test these changes on the AB Jul 29 22:48:58 JPEW: are you ok with something like http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=6777b3db3dfd5ead66a89130376780365b6347a9 (turning unihash into a mixin class)? Jul 29 23:36:15 RP:figured that, I dropped them from my master-next for now Jul 30 01:36:36 How's it going everyone? I'm trying to build a basic gumstix-console-image on a gumstix poblano board. when i go to bibake i the following error: $ bitbake gumstix-console-imageLoading cache: 100% |############################################| Time: 0:00:00Loaded 657 entries from dependency cache.ERROR: ParseError at /home/dev/Documents/ariesos Jul 30 01:36:36 /yocto/poky/meta-gumstix/recipes-bsp/u-boot/u-boot-fslc.inc:6: Could not inherit file classes/fsl-u-boot-localversion.bbclass Jul 30 01:37:01 i'm new to yocto so i'd welcome any pointers on where to look in the documentation to fix this. Thank you in advance! Jul 30 01:44:50 FailDev: it seems you need meta-freescale layer Jul 30 02:02:13 ok i'll give that a shot - thank you! **** ENDING LOGGING AT Tue Jul 30 03:01:12 2019