**** BEGIN LOGGING AT Tue Mar 17 02:59:57 2020 Mar 17 07:48:18 New news from stackoverflow: How to have more than one tty console in yocto? Mar 17 09:03:38 hi, i have a kernel config fragment (generated via menuconfig/diffconfig), which is copied to $WORKDIR but for some reason completely ignored afterwards during kernel compile Mar 17 09:03:51 what could be the reason for such a behavior? Mar 17 09:04:21 shouldn't resolve menuconfig/diffconfig all dependencies? Mar 17 09:15:31 Dracos-Carazza: depends on the recipe handling your kernel fragment. If it does not inherit kernel-yocto (or yocto-kernel?) bbclass, if it's not manually implemented in your recipe, you don't have fragment support Mar 17 09:16:23 fragment support is activated Mar 17 09:16:38 there are several fragments from different layers Mar 17 09:32:16 Dracos-Carazza: 1) check there isn't already a fragment named like that somehwere else. 2) check it's correctly named (e.g. has the correct file extension or whatever is used to detect it's a config fragment) 3) check the different config fragments you have are not conflicting in some ways (though I think Yocto throws an error when that happens?) Mar 17 11:08:25 hi is there a way to SKIP a specific .bbappend for an image ? Mar 17 11:09:08 for an image, no Mar 17 11:09:42 mauz555: https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-BBMASK, yocto-wide unfortunately Mar 17 11:10:54 images are build from packages whihc are built from recipes. bbappend changes a recipe but will impact the packages which are used in all images Mar 17 11:11:42 mauz555: but depending on what's inside the bbappend, you could actually override it in another bbappend? Mar 17 11:12:35 im setting up a production image and development image derived from prod adding dev tools Mar 17 11:13:40 I bbappend systemd-network to automatically set up wlan connection for the dev image. but Id like to skip this .bbappend for the base (prod) image Mar 17 11:14:57 have two recipes that ship different configuration Mar 17 11:16:35 you can just ship the configuration fragments in their own recipe Mar 17 11:16:38 no need to bbappend Mar 17 11:16:57 I guess I'd better copy and rename the whole systemd-conf recipe from poky/meta to my own layer and make it one for prod and one for dev, so I could easily add them specifically per images Mar 17 11:17:36 no need Mar 17 11:17:46 the entire point of systemd configuration is that you can drop in fragments Mar 17 11:18:24 rburton: what do you mean by "ship the configuration fragments" Mar 17 11:19:23 mauz555: e.g. files under /etc/systemd/network/ Mar 17 11:20:26 I shipped systemd-network files to my own layer, but i needed a systemd-conf_%.bbappend to "FILESEXTRAPATHS_prepend" and "do_install_append" and "FILES_${PN}" Mar 17 11:20:44 No, you can install them from another recipe too Mar 17 11:20:48 See e.g. https://github.com/QtiPi/meta-qtipi/blob/master/recipes-core/network-config/network-config.bb Mar 17 11:21:18 Maybe not the prettiest recipe in the world, but you can get the point from it :) Mar 17 11:21:19 okay so I can just rename systemd-conf_%.bbappend to mysystemdconf-prod.bb for example Mar 17 11:22:05 aewsome! ty erbo, rburton, qschulz Mar 17 11:22:09 You probably need more than a rename, but yes that's the basic idea. Mar 17 11:24:54 technically, this can be done in a bbappend with a new package in PACKAGES right? (just asking) Mar 17 11:25:38 yeah Mar 17 11:25:42 more complex that way though Mar 17 11:25:50 might as well just have a single recipe shipping the fragment Mar 17 11:27:18 rburton: ah? PACKAGES =+ "${PN}-myconf" and then FILES_${PN}-myconf = "/etc/systemd/network/myconf.file"? isn't that enough? (with the added install in do_install) isn't that enough? Mar 17 11:27:47 i just think its neater to not bbappend if you don't need to Mar 17 11:27:59 rburton: agreed. Mar 17 11:39:50 also I needed a systemd_%.bbappend to add PACKAGECONFIG_append = " networkd resolved". could I instead use some kind of DEPENDS_${PN}-systemd in my network-config.bb ? I know it works for packages but does it works for PackageConfig ? Mar 17 11:40:13 mauz555: No, that bbappend is still needed Mar 17 11:40:25 One package cannot affect how another one is built Mar 17 11:40:37 In the same way images can't to that Mar 17 11:41:09 Since packages are built the same way regardless of which image they might eventually end up in Mar 17 11:41:15 LetoThe2nd: it's time for your cult anthem now. Hurry up ^^^^^^ Mar 17 11:41:33 erbo: clear Mar 17 11:43:31 erbo: as I cannot mask a specific bbappend for a specific image and as PACKAGECONFIG_append can only happen in a bbappend. I guess my production and developement image will have to share that behaviour. Mar 17 11:44:30 mauz555: yes, but I guess having networkd enabled can't have that many downsides unless you're really space contrained Mar 17 11:46:05 erbo: right. I measuring how much I can reduce the "attack surface" using different images Mar 17 11:50:45 mauz555: if it's really an issue, you might want to have a look at different distros? that way you can have PACKAGECONFIG_append_distrowithnetworkd = " networkd resolved"? Mar 17 11:51:10 but be careful, having different distros means almost everything is rebuilt and have a different sstate-cache Mar 17 12:57:24 do you know how to call "source oe-init-build-env" and "bitbake core-minimal-image" inside a shell script? The first command doesn't continue to the second. Mar 17 13:01:21 try to check return value of command Mar 17 13:08:39 mckoan: might need a subshell or source your script? Haven't tested though Mar 17 13:14:26 qschulz: I am not sure is possible to surce a script that is doing a source Mar 17 13:14:50 the problem here is that the source is inside a script Mar 17 13:15:15 so it doesn't exit and can't continue to the next command Mar 17 13:17:57 mckoan: we're doing it, so yes, you can :) Mar 17 13:18:34 (though we're not calling bitbake in it, but source oe-init-build-env followed by our logic "works" TM) Mar 17 13:24:16 Hi, I would like to build a custom application for a Yocto target. I figure the proper way to do that is to use the eSDK. I am using the same (linux) host to develop & build both the Yocto system and the application. Mar 17 13:24:16 Can I run the eSDK (particularly, devtool) directly from the Yocto source tree without having to (re-)build (bitbake image -c populate_sdk_ext) and install it each time I change something in the image? Mar 17 13:42:11 qschulz: solved, it works if you use #!/usr/bin/env bash instead of #!/bin/bash ;-) Mar 17 13:53:57 mckoan: could this mean that you don't have bash in /bin ? Mar 17 13:55:14 yeah that sounds wrong Mar 17 13:55:39 the only reason source followed by bitbake won't work is if you're not actually running a shell script, but a series of shell commands in different shells Mar 17 13:56:04 like in a makefile you can't do source oe-init-build-env and then bitbake on the next line: theyre different shells so the environment doesn't persist Mar 17 13:56:12 source oe-init-build-env && bitbake foobar Mar 17 13:56:15 is the solution there Mar 17 13:57:46 rburton: that takes a very long one liner if you have many things to do :) Mar 17 14:05:57 rburton: actually my script contains only these two lines Mar 17 14:06:45 rburton: but the solution was to change the shebang Mar 17 14:07:43 mckoan: I think the point of using /usr/bin/env bash is for portability, if someone uses your script on a system where bash is not in /bin as in your first try Mar 17 14:09:00 yeah I don't understand why it made a difference Mar 17 14:33:46 erbo: actually you are right, I'm still digging Mar 17 14:42:44 Erlkoenig: devtool is available right in the standard build environment, no need to do the esdk dance at all. Mar 17 14:44:41 Hey there, ok, this seems very basic but still I am failing... I managed to get ssh access to a qemu image. But this fails on the actual device. I added `IMAGE_FEATURES += "ssh-server-dropbear"`. Is there any other configuration required? the device boots but on ssh using user `root` it says "No route to host" Mar 17 14:45:33 Got it! Mar 17 14:46:26 No way! my router front end is showing wrong IP addresses ... fucking cheap included Vodafone routers! Suckers... Found the correct ip using `nmap` Mar 17 14:46:49 That took about two hours... grrr Mar 17 14:48:23 LetoThe2nd: and it automatically uses all the dependency recipes and compilers from the source tree? Mar 17 14:48:44 emrius: I usually find it helpful to connect to the target via serial port terminal, issue "ifconfig" and then connect via SSH... Mar 17 14:49:22 Thanks! Yeah, I have to get used to that workflow Mar 17 14:49:40 New news from stackoverflow: Step by Step walk through on how to use swupdate on Raspberry Pi or any Embedded board for system update Mar 17 14:51:12 Erlkoenig: yes, devtool works with bitbake. I'm not sure if these words are exact but yes, you can devtool modify my-recipe, devtool build and even devtool deploy-target Mar 17 14:52:32 Okay thanks... Right now I'm working on a different issue: Yocto uses g++ 7.3.0 but I need 8.3.0 - actually, I have a working aarch64-linux-gnu-g++ installed... Mar 17 14:54:48 Erlkoenig: I'm not familiar with compilers, why do you depend on a specific g+ version? IIRC, it's recommended to take the one from the Yocto branch and not try to backport/update it. So if need be, update your layers? Mar 17 14:54:50 Erlkoenig: then you have to set up a yocto build that brings the desired compiler. Mar 17 14:55:12 Erlkoenig: .e.g listen to qschulz ... (me is off again) Mar 17 14:55:27 g++ 7.3.0 appears to have some bugs with C++17 that are fixed in 8.3.0 Mar 17 14:55:35 Currently trying to workaround Mar 17 14:56:23 Erlkoenig: who uses C++? just migrate to pure C Mar 17 14:56:36 I use it Mar 17 14:57:18 I was trolling :) Mar 17 14:57:21 we're too Mar 17 14:57:45 Gah! My blood pressure was peaking. Mar 17 14:58:14 Erlkoenig: warrior branch has g++ 8.3.0 (well, gcc, but I don't see why we would have two different versions for gcc and g++) Mar 17 14:58:41 okay... I am using a sumo tree provided by the board manufacturer Mar 17 14:58:58 YPTM armin is on Mar 17 15:00:21 YPTM: Joshua Watt here Mar 17 15:00:26 I seem to have found a workaround. I think that's okay for now... Mar 17 15:00:27 YPTM Scott Murray is on Mar 17 15:00:37 YPTM Tim is on Mar 17 15:00:54 Erlkoenig: maybe you could share this workaround? people might have the same question in a few days/months Mar 17 15:01:23 YPTM Michael present. Mar 17 15:02:04 I was capturing a template parameter pack in a lambda and extracting it in that lambda. I now wrapped that in another lambda that gets called for each parameter pack entry and which internally only sees single entries Mar 17 15:02:13 Making a minimal example for that might prove difficult Mar 17 15:06:13 I'd like to make yocto cross-compile a custom cpython extension module, but haven't found much prior art on calling 'setup.py build_ext' from a .bb file. Mar 17 15:25:21 Erlkoenig: I thought it was Yocto related work around :'D But thanks! Mar 17 15:25:34 ah :D no i modified the source code Mar 17 15:50:49 YPTM minutes: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4 Mar 17 15:51:19 damn, that's fast! Mar 17 15:52:55 khem: the YP autobuilder for zeus has gcc/glibc/binutils 'ptest' resutls: https://autobuilder.yocto.io/pub/non-release/20200313-3/testresults/testresult-report.txt Mar 17 15:53:24 I didn't see them for master, maybe armpit knows if the are only run for released versions. Mar 17 16:02:30 thaks vmeson its helpful Mar 17 16:04:34 Hey folks, I just posted another question on SO: https://stackoverflow.com/questions/60726034/how-to-handle-the-license-field-when-there-is-no-license-file Mar 17 16:04:45 What if there is no license file? Mar 17 16:06:28 what is the license? Mar 17 16:06:36 GNU Mar 17 16:06:41 and where is that defined Mar 17 16:06:51 in each file header it seems Mar 17 16:07:11 e.g. https://github.com/jwrdegoede/rtl8189ES_linux/blob/master/platform/platform_ops.h Mar 17 16:07:42 and there we go, a license file Mar 17 16:07:53 you can tell the license checksum to use a piece of the file with beginline/endline Mar 17 16:08:30 ok. Great, I'll do that. I was just not sure if there is an issue as there are basically about 100 license copies. Mar 17 16:08:50 Anyway, I open an issue on the root repo asking to add a dedicated file. Mar 17 16:08:57 thanks Mar 17 16:08:59 you can just do one of them Mar 17 16:09:04 vmeson, we have them for m3 Mar 17 16:09:06 find a central header or something Mar 17 16:09:08 https://autobuilder.yocto.io/pub/releases/yocto-3.1_M3.rc1/testresults/testresult-report.txt Mar 17 16:09:21 Ok Mar 17 16:10:03 You want to answer the question to get the credits on SO or shall I do that? Mar 17 16:12:32 A little grepping in my yocto install and I see a couple of instances of "${PYTHON} setup.py" which looks promising, but no examples of build_ext Mar 17 16:19:56 New news from stackoverflow: How to handle the LICENSE field when there is no license file? Mar 17 16:21:52 emrius: done Mar 17 16:22:02 thanks Mar 17 16:22:27 accepted :) Mar 17 16:40:36 LetoThe2nd, qschulz - devtool appears to work right out of the yocto source tree, thanks! For whatever reason it didn't work right away when I first tried. Even deployment works, nice... Mar 17 16:46:49 If I have an IvyBridge cpu for a machine, should I create my ivybridge-tune, so that I can get the AVX instruction set? Because If I use the corei7, it doesn't come with the AVX instruction set. Mar 17 16:48:52 any examples of building a basic python extention module in yocto? Mar 17 17:20:55 roussinm: meta-intel master has a shiny new BSP especially for you Mar 17 17:22:12 roussinm: try intel-skylake-64, *should* be an improvement. you'll want to double-check that skylake doens't add stuff that ivybridge doesn't have, i can't remember what was added when Mar 17 17:24:49 shiny.. nice Mar 17 17:34:01 rburton: thanks, I'll take a look, but we are stuck on Krogoth. Mar 17 17:34:28 then the skylake bsp is a perfect example of how to make your own custom bsp i guess Mar 17 17:34:40 amazing thanks! Mar 17 17:35:32 We are trying to get the most juice out of this machine lol :/ We were thinking of maybe backporting gcc 9.2 only for that machine, but it's probably too much work for the gain. Mar 17 17:40:15 rburton: would you accept a patch to add the tune for ivybridge inside the meta-intel layer? Mar 17 17:43:18 I'm surprised by gcc-runtime-dbg not containing the source files - is there something to look for around gcc-source package ? Mar 17 18:30:47 yann: just a guess on my part but perhaps gcc-runtime-dev? Mar 17 18:49:53 I am trying to devtool build some-recipe in an eSDK I created. I am isntalling the eSDK in a docker container (not sure if that is relevant). My recipe downloads a git repo (camke is used here). Does anyboday knows what coudl be the reason of having "/bin/sh: 1: commonapi-generator-linux-x86_64: not found" returned on a "add_custom_command"Hello Mar 17 18:50:18 That last "Hello" word was supposed to be at the beginning of my line Mar 17 18:50:53 for a little more detail on my recipe, you can take a look here - the recipe is really short: https://lists.yoctoproject.org/g/yocto/message/48782 Mar 17 18:53:31 if I run that same command (i.e. commonapi-generator-linux-x86_64) anyware on my docker container, the command will be found and executed. Only when I am trying to build my recipe, will the command not be found Mar 17 19:32:23 milloni: there's no such package - libstdc++-dev in my case is the closest, bus as expected only contains the headers, not the libstdc++ sources Mar 17 19:33:35 hmm, okay, another guess - won't it be basically the same source as gcc-dev? Mar 17 19:46:12 hello how do you change the machine network hostname using poky ? Mar 17 19:51:18 this does not work https://www.yoctoproject.org/docs/2.7.3/mega-manual/mega-manual.html#usingpoky-extend-customimage-image-name Mar 17 19:55:54 mauz555: this does work, i have personally tested it only a couple of days back. the important parts ar the lines above the snippets, which sate in which files those things are expected to be placed. Mar 17 20:04:48 [RFC] how about a form of the build-appliance (dev-appliance?) that incorporates an esdk? multiconfig should makes this pretty straightforwards, right? Mar 17 20:18:09 LetoThe2nd: I'm not sure I quite follow what you are trying to do Mar 17 20:19:35 JPEW: we have the build-appliance image which is basically just an image with packagegroup-self-hosting on steroids, right? Mar 17 20:20:23 It's designed to produce an image that can build Yocto correct? Mar 17 20:20:49 That you could run e.g. in a container, in qemu, on a PC, etc. Mar 17 20:20:54 JPEW: yeah, thats how i read it. Mar 17 20:21:12 LetoThe2nd: So you want to build one that already has the eSDK in it? Mar 17 20:21:19 JPEW: bingo. Mar 17 20:22:53 LetoThe2nd: Whats the use case? Mar 17 20:23:48 JPEW: having something that can be handed out along a specific board/target for newbies to start out more easily. Mar 17 20:24:27 Hmm, I've not used the eSDK much... is it a lot better than bitbake itself? Mar 17 20:24:36 s/better/easier/ Mar 17 20:24:58 JPEW: its different and makes some specific workflows more straightforward. Mar 17 20:25:19 JPEW: e.g. devtool specifically. Mar 17 20:25:36 LetoThe2nd: is there no way to make it work from an image bb file ? I'd like to have a different hostname based on the loaded image Mar 17 20:25:47 i just thought of the esdk as it would be an easier path than actually baking in a complete build environment. Mar 17 20:25:58 mauz555: nope, it doesn't work like that. Mar 17 20:26:51 mauz555: You *might* be able to override in a post processing command Mar 17 20:28:23 (yeah there are always tricks around it, like setting the hostnmae per se to empty, and injecting something else via a magic recipe that in turn pulls from somewhere... but thats a) a lot of work b) prone to break c) so much black magic - that the down to earth answer is just "no") Mar 17 20:28:46 yocto is the most funny piece of technology I met, yet in the end it seems to do the job as intended Mar 17 20:30:44 blackmagic right Mar 17 20:32:54 JPEW: so weirded out by the line of thought? Mar 17 20:43:49 LetoThe2nd: heh, not sure :) Mar 17 20:44:04 LetoThe2nd: Trying to figure out how multiconfig plays into it Mar 17 20:45:20 JPEW: mc1: make the esdk. mc2: make the appliance, incorporating result from mc1 Mar 17 20:46:07 reasoning is that the target is a specific image-machine-distro config, which almost certainly is not x86_64/build-appliance :) Mar 17 20:50:53 LetoThe2nd: Right, so I think you could write a recipe for the build appliance that extracts the eSDK so its included in the image Mar 17 20:51:31 So, the next question is: Why is the build-appliance necessary? Mar 17 20:55:55 JPEW: so everything is already neatly wrapped up for those who are not familiar with the process of setting the stuff up Mar 17 21:02:21 * LetoThe2nd anyways, calls it a day. Mar 17 21:20:53 LetoThe2nd: i'd be inclined to embed a proper bitbake and not esdk tbh Mar 17 22:23:40 hmm, I'm being asked for good intermediate-level tutorials Mar 17 22:23:58 perhaps LetoThe2nd's twitch recordings? Mar 17 22:29:00 probably a good start yes **** ENDING LOGGING AT Wed Mar 18 02:59:58 2020