**** BEGIN LOGGING AT Mon Oct 29 03:00:01 2018 Oct 29 08:25:59 <_mac13_> Hi, I've need to compile kernel using different GCC version then for user-space application, what is the best approach to achieve that? I've been thinking about custom bbclass for kernel recipe Oct 29 08:50:25 good morning Oct 29 08:51:03 mckoan: as usual, agreed on the "morning" part Oct 29 08:51:20 LetoThe2nd: LOL, hi Oct 29 08:51:53 LetoThe2nd: your beer was an excellent opticalexperiment ;-) thanks Oct 29 08:52:09 mckoan: you're welcome :) Oct 29 09:03:23 New news from stackoverflow: Bitbake: "The metadata is not deterministic and this needs to be fixed" Oct 29 09:17:01 What is the "proper" way to have one recipe run-time-on-target dependable on another? i.e. If I IMAGE_INSTALL recipe A, recipe B will also be installed? It doesn't have any build-dependencies, the artifacts from B just have to be present on the image. Oct 29 09:17:41 jofr: RDEPENDS_${PN} Oct 29 09:18:34 So recipe A will have RDEPENDS_${PN} = "recipe_b"? Oct 29 09:18:52 on package_b, but basically yes. Oct 29 09:19:06 Err. yes. ;) Oct 29 09:41:50 Hi guys. Is it makes sence in FILESEXTRAPATHS_prepend or FILESEXTRAPATHS_append in custom linux*.bbappend file? e.g. from this doc: https://www.yoctoproject.org/docs/2.5/kernel-dev/kernel-dev.html {2.3.3. Changing the Configuration} I see that there are provided FILESEXTRAPATHS_prepend variable.. but my linux*.bbappend already has the FILESEXTRAPATHS_append variable. Oct 29 09:43:01 Currently, my custom linux*.bbappend (with FILESEXTRAPATHS_append) has only the SRC_URI with a set of a patches.. Oct 29 09:43:28 But not I want to add there and the my custom Linux Kernel config file.. Oct 29 09:43:39 s/But not/But now Oct 29 09:44:15 What I need then to do with my previous FILESEXTRAPATHS_append ? Oct 29 09:52:13 how do you people go with repositories for your local versions of yocto? Oct 29 09:52:21 do you have to use that repo thing Oct 29 09:55:58 You don't have to use it. We're using plain submodules, for example. Oct 29 09:56:05 Each of the possible solutions has their upsides and downsides. Oct 29 09:57:06 another option is kas. but yeah, you *have* to do nothing, but find out what fits your need. Oct 29 09:57:16 (you could also use a toaster instance) Oct 29 10:03:34 New news from stackoverflow: Where are bitbake python functions documented Oct 29 10:04:10 Guys, what I need to use: FILESEXTRAPATHS_prepend or FILESEXTRAPATHS_append? if I want to use both my kernel patches and my defconfig? Oct 29 10:20:11 It only matters if you have the same file name in multiple layers... Oct 29 10:20:59 With prepend you can make sure that your extra path will get examined earlier... Oct 29 10:23:01 sagner: Hmm.. I have added my defconfig to *.bbappend file: Oct 29 10:23:03 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" Oct 29 10:23:03 SRC_URI += "\ Oct 29 10:23:03 file://defconfig \ Oct 29 10:23:49 but what I do bitbake my-image, I see that a default config file in 'workdir' is a not my defconfig file! Oct 29 10:24:02 s/but what/but when Oct 29 10:24:23 my defconfig file is ignores Oct 29 10:25:42 kuzulis: use bitbake -e to figure out which paths are exactly checked. They are checked in order, make sure that yours is early enough Oct 29 10:27:25 sagner: bitbake -e linux-toradex prints out a lot of info.. I don't know what I need to take from.. Oct 29 10:28:51 kuzulis: I usually redirect it in a file and then examine that Oct 29 10:29:38 kuzulis: you want to check the FILESEXTRAPATHS variable Oct 29 10:32:17 sagner: I see that contains following FILESEXTRAPATHS=::__default: Oct 29 10:32:52 kuzulis: the problem is probably that toradex uses FILESEXTRAPATHS_prepend too, then its a question which layer gets parsed first Oct 29 10:33:03 kuzulis: try reordering layer include in bblayers.conf Oct 29 10:33:20 e.g. put yours before/after meta-toradex* Oct 29 10:34:18 sagner: Currently my layer is declared after all other layers.. Oct 29 10:34:59 sagner: So, what I need to expect in FILESEXTRAPATHS ? Oct 29 10:35:20 sagner: Shoul my layer be on a first place there? Oct 29 10:35:46 sagner: I mean my path to my kernel recipe on a first place? Oct 29 10:40:10 But, it is strange, why my patch in FILESEXTRAPATHS is after the '/meta-toradex-nxp' path? Because my layer is declared after the layer.. So, as I understans, my 'prepend' should be called in end of a script.. So, my path should be in a first place..> Oct 29 10:40:21 khem: hello, it seems your recipe for libxcrypt fails to fetch on poky master: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/libxcrypt/libxcrypt_4.1.1.bb?h=master Oct 29 10:40:43 khem: Github repository does not have a master branch Oct 29 10:41:07 khem: the commit is on develop branch, though Oct 29 10:44:35 Why this does not work? Oct 29 10:44:36 If you have a final Linux kernel .config file you want to use, copy it to a directory named files, which must be in your layer's recipes-kernel/linux directory, and name the file "defconfig". Then, add the following lines to your linux-yocto .bbappend file in your layer: Oct 29 10:44:37 FILESEXTRAPATHS_prepend := "${THISDIR}/files:" Oct 29 10:44:37 SRC_URI += "file://defconfig" Oct 29 10:44:37 Oct 29 11:47:20 morning Oct 29 11:53:13 rburton: Hi. Could you please help me with using my 'defconfig' ? Because it ignores.. Oct 29 11:55:17 kuzulis: I think the order bbappend's get applied are determined by the layer priority Oct 29 11:56:22 sagner: Do I need to increase a my layer priority? A higher value means a highest priority in yocto? Oct 29 12:10:09 kuzulis: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-BBFILE_PRIORITY Oct 29 12:12:18 ok, many thanks Oct 29 12:27:06 sagner: A layer's priority does not work too.. E.g. the 'meta-toradex-nxp' layer has priority 90... So, I have added priority 91 to my layer.. And I see that the defconfig file takes from the meta-toradex-nxp layer. Oct 29 12:37:05 rburton: hello, any idea when official working release of Thud is expected? I believe the wiki says it was supposed to be ready this month Oct 29 12:37:27 eduardas_m: shortly. you can start testing with the thud branch now if you want Oct 29 12:37:49 rburton: I actually am at this very moment Oct 29 12:38:05 kuzulis: and you use a bbappend file? Oct 29 12:38:34 rburton: there is a fetch failure with libxcrypt Oct 29 12:39:15 rburton: recipe defines the branch to be master, but there is no such branch in github repo Oct 29 12:39:39 eduardas_m: patch on the list, s/master/develop/ Oct 29 12:48:03 RP: need the xcrypt patch in thud (in my branch) Oct 29 12:50:33 rburton: agreed Oct 29 12:50:43 sagner: Wow.. Seems it work whet I put my defconfig file inside of new 'apalis-imx6' directory of my recipe Oct 29 12:50:54 Guys, many thanks Oct 29 12:51:06 s/whet/when Oct 29 12:52:59 kuzulis: try bitbake-layers show-appends linux-toradex Oct 29 12:55:28 sagner: https://pastebin.com/cZG7vTQn Oct 29 13:08:41 eduardas_m: re release, the weekly status has an update. '· 2.6 M4 is due to be built as soon as we have the oeqa reporting patches merged. Oher changes which put the release at risk will be deferred to master.' Oct 29 13:14:13 kuzulis: oh yeah that makes sense, because the original defconfig is probably in a machine specific subfolder too Oct 29 13:14:15 rburton: this might sound stupid, but I do not really understand what purpose do M versions serve... are these the equivalents of kernel.org release candidates? also, is there a document that explains the Yocto project release process? Oct 29 13:14:27 milestone releases Oct 29 13:14:54 https://wiki.yoctoproject.org/wiki/Yocto_Project_Release_Process Oct 29 13:15:13 rburton: thank you Oct 29 13:19:33 rburton: so as far as I understand milestone releases give no real guarantees on what standard targets build with them? Oct 29 13:19:58 well we don't release known broken milestones Oct 29 13:20:04 they're entirely for development purposes though Oct 29 13:20:28 mainly for scheduling and ensuring the quality of master isn't totally broken Oct 29 13:27:24 is anybody else noticing broken behavior with `install`? i.e. single step `install -dt foo source/*` does *not* wor, while two step`install -d ...`, `install -t foo source/*` works. Oct 29 13:33:51 I assume it's related to selinux -.-' Oct 29 13:34:37 am loving how it 'randomly' interferes and crushes recipes that used to work O.o Oct 29 14:08:19 is it planned that all systemd configuration customizations should be handled as systemd-conf recipe bbappends that are machine-specific starting with Thud? Oct 29 14:08:36 question related to commit: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=28c2f0dfe3ae06d87772b2a88fcace5a03e09143 Oct 29 14:09:31 or am I supposed to just override the recipe entirely? Oct 29 14:35:43 Can anyone help me solve this error https://pastebin.com/5eBw37SW Oct 29 15:01:04 Hi, is it possible to run a sudo command as part of recipe ? could anyone point me for doing so Oct 29 15:01:27 no Oct 29 15:01:38 well, yes, if you configure sudo to not ask for auth Oct 29 15:01:45 better question is why do you want to run a sudo task Oct 29 15:02:31 sudo rm -rf / Oct 29 15:02:38 hahaha Oct 29 15:03:18 rburton: i want to create a img file for SD card for which I wanted to run losetup commands Oct 29 15:03:30 you don't need sudo to set up a disk image. use wic Oct 29 15:04:34 Guys.. I tried to do: bitbake -c menuconfig virtual/kernel ... but it faild with do_menuconfig: No valid terminal found, unable to open devshell. Oct 29 15:04:40 What does it means? Oct 29 15:04:49 What I need todo to fix it? Oct 29 15:06:37 Ahh.. I need in: sudo apt-get install screen Oct 29 15:06:42 kergoth: thank you this what I was looking for :) Oct 29 15:09:34 Guys, does 'bitbake -c menuconfig virtual/kernel' puck-up my custom kernel config? I mean that defconfig, which uses in building of a kernel? Oct 29 15:13:23 kuzulis: I don't think that menuconfig works with the Toradex bsp layers Oct 29 15:13:39 is it possible to use PACKAGECONFIG to add an RDEPENDS value only for a single package instead of the whole recipe? Oct 29 15:14:18 sagner: Why? I run menuconfig, and I see it UI. Oct 29 15:14:35 CoLa|work: it does that already, it adds it to RDEPENDS_${PN} Oct 29 15:14:43 so it's not the wohle recipe, it's ju st the main package Oct 29 15:14:49 but no, you'd have to use inline python to do it Oct 29 15:15:07 kuzulis: I am not sure, I just remember that somebody had issues with it once.. Maybe this helps? https://www.toradex.com/community/questions/585/how-to-use-menuconfig-on-console-trdx-image.html Oct 29 15:16:05 kergoth: thanks, will have to go with inline python then since only ${PN}-fooplugin shall gain an RDEPENDS and not ${PN} Oct 29 15:16:32 should be pretty straightforward using the contains() function on PACKAGECONFIG. grep around oe-core,k you'll find examples Oct 29 15:16:38 sagner: Hmm.. in my case it works: bitbake -c menuconfig virtual/kernel Oct 29 15:16:47 there are mu ltiple recipes for whom the default packageconfig handling isn't entirely sufficient on its own Oct 29 15:17:02 sagner: And seems, it puck-ups my kernel config.. Oct 29 15:17:20 s/puck-ips/pick-ips Oct 29 15:17:25 s/puck-ips/pick-ups Oct 29 15:18:08 sagner: But menuconfig's UI looks ugly Oct 29 15:22:16 sagner: like: https://imgur.com/a/VN3yKoG Oct 29 15:23:19 Does know anybody, to what directory a new kernel config will be saved? Oct 29 15:23:47 after menuconfig ? it is just the kernel build’s .config Oct 29 15:23:52 i.e. ${B} Oct 29 15:24:25 Do you mean is in working directory ? Oct 29 15:24:34 nope Oct 29 15:24:36 I mean ${B} Oct 29 15:24:53 the build dir, is not the workingdir, they are two separate things. Oct 29 15:25:29 do you mean, like: /build-apalis-imx6/tmp/work/apalis_imx6-poky-linux-gnueabi/linux-toradex/4.1-2.0.x-2.7.5/build Oct 29 15:25:35 ? Oct 29 15:25:56 should be yah. but I don’t know the kenrel recipe you are using, so in theory, it could be different. Oct 29 15:26:12 ok, many thanks Oct 29 15:26:45 maybe someone know, why a menuconfig UI looks ugly: https://imgur.com/a/VN3yKoG ? Oct 29 15:26:48 :) Oct 29 15:27:17 likely just a result of the terminal you are using. Oct 29 15:27:35 I use remote SSH conenction Oct 29 15:27:40 connection Oct 29 15:27:47 could be that as well. some translation on the codes. Oct 29 15:28:17 ok Oct 29 15:28:37 but 'mc' utility works good Oct 29 15:29:27 afaik, menuconfig uses ncurses too (as and 'mc') Oct 29 15:41:02 morning/afternoon... im considering a build cluuster for arm64 but im seeing an anomoly building sayy chromiuum for raspberrypi3 ... odd to me since it X builds fine on an intel for rapspberrypi3 Oct 29 15:46:44 arm as host is obviously fairly untested as only recently has it become feasible Oct 29 15:46:53 should work, but no doubt there are recipes which don't Oct 29 15:47:26 we actually have a new arm hosting waiting to be installed in the test racks so it will become more tested but we're not there yet Oct 29 15:48:18 tbh not surprised you mention chromium at all :) Oct 29 15:48:44 rburton: in terms of expecting it to break? ;-) Oct 29 15:48:56 hell yeah! Oct 29 15:50:29 just odd so i changed the recipe to raspberrypi3-64 to see if that faired any better Oct 29 15:52:00 rburton: hrhrhr Oct 29 15:53:20 https://pastebin.com/s8GLGTJP of the chromium failure from xcross on arm64 Oct 29 15:53:46 any thoughts? other then dont expect it to work :P Oct 29 15:56:12 every other recipe build fine, even x and freinds Oct 29 16:14:26 RP i had a AB failure with a traceback from the builder code. I don't see what I may have done wrong.. restarted the build Oct 29 16:16:11 armpit: oe-core repo, not poky? Oct 29 16:18:04 RP poky contrib noted Oct 29 16:18:10 right branch Oct 29 16:18:39 is "mut" a keyword? I used akuster/mut Oct 29 16:19:02 or is akuster a keywork == failure ; ) Oct 29 16:19:15 armpit: you told it there was a poky derived tree there and there isn't Oct 29 16:19:25 armpit: ross/mut is poky derived Oct 29 16:20:25 right I see now Oct 29 16:22:34 opkg_prepare_url_for_install: Couldn't find anything to satisfy 'drived'. do_rootfs: unable to install packages. Any idea what's going on here? Oct 29 16:31:17 Hello! Is there any difference between using recipies from oe-core and meta-networking (spoiler alert: stuff from oe-core works for me, but not from meta-networking)? Oct 29 16:34:13 AFAIK both are part of OpenEmbedded. Oct 29 16:39:25 why isn't my recipe getting built into a .ipk file? I'm inheriting native, does that have anything to do with it? Oct 29 16:43:57 armpit: I killed off some obsolete builds to give you more workers Oct 29 16:44:18 k Oct 29 16:44:50 thanks Oct 29 16:51:20 noway96, pretty sure native recipes do not get packaged Oct 29 16:51:55 Crofton|work so why is that? Oct 29 16:52:07 and how are they installed? Oct 29 16:52:59 Crofton|work where should I specify them such that they're added to the image? Oct 29 17:03:38 oh nm I guess it's meant for the build host and not the target machine so the correct answer is - you can't Oct 29 17:13:36 armpit: I should also note you are slowing my handling of the release by doing this :/ Oct 29 17:16:37 then my build should be killed. Oct 29 17:16:56 I need the target Linux kernel src headers available during my recipe's compilation. How do I do that exactly? Oct 29 17:17:07 the release has priority Oct 29 17:17:56 * armpit stops build Oct 29 17:18:04 armpit: not much point now, just worth realising it does mean my build won't finish so quickly :/ Oct 29 17:19:05 armpit: but thanks, 2.6 is taking far too long. Not been able to concentrate properly on patches until today due to illness :( Oct 29 17:20:05 I'm very likely to take what is in -next as 2.6 rc1 FWIW. If anyone knows of anything critical not in there, speak now... Oct 29 17:20:09 sorry to hear Oct 29 17:20:26 armpit: conference 'flu' :( Oct 29 17:20:41 at least no jetlag Oct 29 17:20:49 train lag ? Oct 29 17:20:53 armpit: :D Oct 29 17:20:54 hmm, cold? I have a not so bad one Oct 29 17:21:15 Crofton: yes, was a cold but just knocked me out a bit :( Oct 29 17:21:48 was it running around in shorts and tee shirt? Oct 29 17:22:07 armpit: no, that probably helped ;-) Oct 29 17:22:08 * armpit was bloody cold at ELCE Oct 29 17:22:21 armpit: temperature has dropped since then Oct 29 17:23:13 the temp at home is 2x that of Edinburgh Oct 29 17:23:34 fray visited the north east after ELCE and would agree the wind here is much worse :) Oct 29 17:24:17 armpit: car said 3C yesterday and lots of traffic accidents on ice Oct 29 17:24:57 Guess I got out in time Oct 29 17:28:25 Is JaMa here by chance? Oct 29 17:30:53 * armpit looks at -next Oct 29 17:34:56 RP one thing to consider are timezone updates. if not now, would have to be in THUD before year's end Oct 29 17:38:41 armpit: I wondered about that. I've taken them and will hold you responsible for all failures :) Oct 29 17:41:30 NP, they all ready had one pass on the AB so I have a more confidence in those changes Oct 29 17:42:29 2018g is out but it can easily wait till later Oct 29 17:43:28 armpit: I set the build away so it will have to :) Oct 29 18:00:59 Question for anyone here, has anyone talked about maintaining deb and rpm packages for the yocto project for major Linux distro's? Oct 29 18:01:24 Well in particular bitbake. Oct 29 18:01:26 junland: not sure i follow that Oct 29 18:01:31 ahhh' Oct 29 18:01:36 Yea. haha Oct 29 18:15:04 my sysroots folder does not have a filled in uapi subfolder. How do I add those contents? Oct 29 18:17:32 the headers should be inside /sysroots/genericx86-64/usr/include Oct 29 18:26:25 junland: at this time bitbake and oe-core, while separate projects, have pretty tightly bound dependencies, and compatibility breaks with more regularity than we'd like, so a system installed bitbake would only work with a limited number of oe-core release versions Oct 29 18:26:39 junland: that's part of why it's used from its repository next to oe-core, to keep them in sync Oct 29 18:32:00 kergoth: Gotcha, thought about maybe getting a rpm spec file going as maybe a for weekend side project. But I guess not since it seems do such a thing would be kinda hard with those dependencies being updated like that. Maybe at a later time? Oct 29 18:32:53 it'd be nice to make bitbake a proper python package that can be installed from pypi or packaged for a distro, and have it work for any oe-core version, but it's really difficult, because our metadata isn't *just* declarative information. Oct 29 18:33:17 tasks, anonymous python, etc often make assumptions about internal bitbake behavior, and there's not a lot we can do about that without a major change to the file format and bitbake both Oct 29 18:38:11 huh, interesting. Oct 29 18:39:24 https://gist.github.com/kergoth/a60046871dfc94a8d7db27f15e5299fd Oct 29 18:56:51 the file poky/meta/recipes-core/uclibc/site_config/headers contains a list of headers which is found inside sysroots/genericx86-64/usr/include. How do I add different headers to this list? Oct 29 18:57:10 .. such that those headers end up in sysroots? Oct 29 19:22:23 anyone? Oct 29 21:25:09 we have a 2.6 M1 build even if it failed to send the QA email Oct 29 21:25:17 halstead: really need to sort the email situation :/ Oct 29 21:26:16 RP Still failing to email. :( Oct 29 21:26:35 halstead: yes: https://autobuilder.yoctoproject.org/typhoon/#/builders/6/builds/164/steps/10/logs/stdio Oct 29 21:26:48 RP I can get on each machine and check them one by one. Oct 29 21:27:17 halstead: we need to sort this as part of machine bringup Oct 29 21:27:35 halstead: this was where I was starting to go with that script Oct 29 21:27:40 email is so last decade, use a forum Oct 29 21:28:02 * RP wonders what throw at Crofton Oct 29 21:28:23 * Crofton grins Oct 29 21:28:36 Yes. That script is the right idea. Oct 29 21:30:27 RP should I send the email again like I did last time? Oct 29 21:30:55 halstead: I didn't know if you were around so I already sent it Oct 29 21:33:59 Excellent. Oct 29 21:34:58 Crofton: I could propose the OE board communicate via a private forum if you like them that much? Oct 29 21:39:18 I'll suggest it Oct 29 21:40:23 Congrats on the RC by the way. Oct 29 21:40:37 armpit: you can have the AB now btw, rc1 built Oct 29 21:40:57 halstead: better late than never? :) Oct 29 21:42:06 Certainly. I suppose the lateness hadn't registered among all the ELC excitement. Oct 29 21:50:53 RP thanks Oct 29 21:51:20 armpit: sorry for interrupting but means rc1 is done now :) Oct 29 21:51:54 armpit: actually can you hold off starting anything for a few minutes please? Oct 29 21:52:30 Crofton, may I suggest morse code Oct 29 21:53:06 RP, np.. I will fire something of in a few hours Oct 29 21:54:41 * armpit Hmm, OE tinder Oct 29 21:57:16 * armpit swipe left for YP, right for OE Oct 29 22:04:04 armpit: thanks, I've pulled the files I wanted off now (oeqa json results) Oct 29 22:04:23 k **** ENDING LOGGING AT Tue Oct 30 02:59:59 2018