**** BEGIN LOGGING AT Fri Apr 24 02:59:57 2020 Apr 24 03:32:03 armpit: something this bizarre can only be related to the tinfoil changes I think :( Apr 24 03:32:31 unfortunately I'm not going to have any time to look at it until next week Apr 24 03:32:57 in the mean time I can put up a notification Apr 24 03:38:00 done Apr 24 03:38:06 also created https://bugzilla.yoctoproject.org/show_bug.cgi?id=13882 to track the problem Apr 24 03:38:07 Bug 13882: normal, Undecided, ---, bluelightning, NEW , layer index: recipe fields being recorded incorrectly Apr 24 05:18:33 New news from stackoverflow: What files to be specified in IMAGE_BOOT_FILES for qemuarm machine while using wic create command Apr 24 07:49:01 New news from stackoverflow: Connect I2C bus,i2cset: write failed: Connection timed out Apr 24 09:59:13 Hi, i wrote a shared object and installed it to the libpath. How can i use this in another recipe? Apr 24 09:59:33 DEPEND on the recipe that builds your shared object Apr 24 10:06:59 I have set DEPEND but do i need to add an include path to the header file manually? Apr 24 10:07:27 PatrickE: Made add a pkgconfig file to go with the shared library? Apr 24 10:07:37 s/Made/Maybe/ Apr 24 10:08:59 I am trying to run my image on qemu and I am getting an error that the "Native sysroot directory....doesn't exist". In fact, it does not, but I am not sure why it is not being built or if I am doing something else wrong. Apr 24 10:10:58 PatrickE: assuming you installed the library to $libdir and headers to $includedir then compiling it normally wil just work Apr 24 10:13:23 erbo pkgconfig? :D Apr 24 10:14:05 rburton i copied it to {D}${base_libdir} Apr 24 10:14:32 libdir is a better choice instead of base_libdir Apr 24 10:16:22 PatrickE: It's a well used way of providing meta data for shared libraries, https://en.wikipedia.org/wiki/Pkg-config Apr 24 10:19:25 you don't *need* that though, it's just helpful Apr 24 10:21:23 Hm Apr 24 10:23:07 Its fine, maybe its a good help to do so. I think it basically should work like i have it now. I checked that bitbake created my libs in the work directory Apr 24 10:23:44 I just get an undefined reference . Include is working now Apr 24 10:24:29 PatrickE: do you add -lyourlib to linker flags? Apr 24 10:25:47 erbo i sed -L but the path was not correct . With -l i get an cannot find examplelib Apr 24 10:26:16 i'm guessing you're using a hand-coded makefile. don't. Apr 24 10:26:37 when writing hand-coded makefiles everyone tries to write more than they need, and break them Apr 24 10:26:43 This is just a testcase... I dont use any makefile atall Apr 24 10:27:01 i call ${CC} in do_compile Apr 24 10:27:16 then you forgot $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) Apr 24 10:27:24 which set the search paths Apr 24 10:28:04 I use CFLAGS and LDFLAGS Apr 24 10:28:14 don't forget CPPFLAGS Apr 24 10:28:44 also assuming that you named the library correctly Apr 24 10:29:09 :) Ok whats important for naming? Apr 24 10:31:30 libfoo.so not foo.so Apr 24 11:02:30 rburton so i name it libexample.so and use -lexample ? Apr 24 11:16:13 * RP can't find whatever in master-next is poisoning master-next builds :( Apr 24 11:24:57 it looks like a small step forward but i still get this error: | /usr/src/debug/exampletool/1.0-r0/exampletool.c:12: undefined reference to `exampleFunc' Apr 24 11:29:59 PatrickE: yes, thats how linkers work. the latest error looks like you broke your library. Apr 24 11:30:33 yes it looks like Apr 24 11:31:28 -dev package contains non-symlink .so: examplelib-dev path '/work/armv7at2hf-neon-fslc-linux-gnueabi/examplelib/1.0-r0/packages-split/examplelib-dev/usr/lib/libexample.so Apr 24 11:31:51 yocto assumes that you're versioning the libraries and makes you do more work if you are not Apr 24 11:32:30 Hm Apr 24 11:32:36 https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries#Non-versioned_Libraries Apr 24 11:33:35 maybe get your library and app working outside of yocto first to reduce the number of things you need to make work Apr 24 11:57:48 Is using Rust for application development in Yocto an "ideal" and "well-supported" method? I am aware of meta-rust, but the general discussion of Rust and Yocto seems nonexistant. Apr 24 11:58:47 I found one mailing list thread from 2017, a blog post that shows how to adjust the Rust compiler to compile for your target machine with values obtained from generating an SDK Apr 24 11:58:56 that was from 2018 Apr 24 11:59:02 yes, just use meta-rust Apr 24 12:09:37 Okay. Let's say I wanted to venture on a Yocto project with some commercial aspiratons, am I much safer sticking to C++? Apr 24 12:11:08 Perhaps this may sound more philosophical, but I'm trying to gauge what is the more sustainable method to work with Yocto. Should I not be disuaded by the non-existant internet chatter about Rust and Yocto? Apr 24 12:12:43 There seems to be a growing Rust-Embedded community, and I don't see Yocto as part of it Apr 24 12:15:49 Don't get me wrong, I'd be happy to publish my own how to on Rust and Yocto, be the solution to my problem.... but I'd like to know if the Yocto community sees Rust as vehicle to adopting a larger audience Apr 24 12:19:17 if you want to use rust, use rust. meta-rust exists and is still being worked on Apr 24 12:28:42 What is the best way to reduce the default 10 second boot timeout that OE sets? Apr 24 12:40:46 What is the best way to reduce the default 10 second boot timeout that OE sets? Apr 24 13:52:00 Hey, I want to group certain settings for development such as runtime dependencies and other configurations into a single class/package/recipe, so that I can do something like `IMAGE_INSTALL_append = " mydevtools"` or so Apr 24 13:52:24 write a pacakgegroup Apr 24 13:52:26 What would be the general strategy for that? Putting everything into a recipe or a packagegroudp Apr 24 13:52:45 a packagegroup is just a recipe that inherits the packagegroup class, which ensures that it just has dependencies and no content Apr 24 13:53:37 hmm.. got kicked out. A too dumb question maybe :] Apr 24 13:53:42 Anyway, thanks! Apr 24 13:59:15 A little followup question: If I gather my dev tools in a packagegroup, can I also configure them from the packagegroup recipe? Let's say I want to configure the `PACKAGE_FEED_URIS` used by `dnf` Apr 24 13:59:48 Can I just throw those environment varaibles into the packagegroup recipe or do I need a dnf_%.bbappend kind of approach? Apr 24 14:15:12 kanavin_home: https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/331 fwiw Apr 24 14:41:51 rburton: LOL Apr 24 14:41:56 rburton: wait a second Apr 24 14:42:25 rburton: ta-daa http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=akanavin/package-version-updates-later&id=07864d27b49e342c16a04b835bafe445a343f6c5 Apr 24 14:42:36 just need a bit of time to submit Apr 24 14:45:50 Hey, i'm trying to boot my image using runqemu so I do runqemu tmp/deploy/images/imx8mn-var-som/b2qt-image-imx8mn-var-som.wic Apr 24 14:46:23 and I get ls: cannot access 'build-imx8mn-var-som/tmp/deploy/images/imx8mn-var-som/*.qemuboot.conf': No such file or directory Apr 24 14:46:34 how do i generate this file? Apr 24 15:20:35 New news from stackoverflow: Facing issue in yocto zeus u-boot compilation Apr 24 16:20:47 New news from stackoverflow: Yocto, export variable to host Apr 24 19:31:49 Hey, quick question: What do I have to add to `IMAGE_INSTALL` to get the c headers, such as `stdlib.h` onto my target? Apr 24 19:39:21 is there a way i can ensure programs are rebuilt if the kernel changes? Apr 24 19:40:29 something changed in our kernel and a userspace program wasn't rebuilt and was broken as a result. i want to understand why this happened. Apr 24 19:49:05 mischief I'm probably the one with the least experience in this channel and haven't used it mysefl but isn't the `buildhistory` class meant to shed some light into that? Apr 24 19:49:35 I just read that chapter in the book I bought :) Apr 24 19:50:19 mischief. did the application's recipe have a kernel dependency ? without knowing anything about the application or recipe, we can only guess. Apr 24 19:53:02 zeddii: no - it's including a header for a macro definition Apr 24 19:53:47 one of the kernel's headers ? i.e. one that isn't in libc-headers ? Apr 24 20:00:56 zeddii: the recipe isnt using the libc headers Apr 24 20:11:40 all good. so that recipe does have a DEPENDS on virtual/kernel ? if so, it should have picked it up. Apr 24 20:13:23 zeddii: it didnt Apr 24 20:13:33 but even now after i added it and try to rebuild the program doesnt work Apr 24 20:13:45 i think maybe the include paths are wrong and its using the libc headers or something. Apr 24 20:14:32 could be. you'd need to have the shared kernel source dir in the include path to get them directly. Apr 24 20:19:54 zeddii: i tried that :) Apr 24 20:20:20 you aren't giving us much to go on. Apr 24 21:06:41 I smell a issue when someone says can I rebuild my app when kernel is recompiled Apr 24 21:27:00 Hi guys. I'm attempting to build b2qt-embedded-qt5-image as shown as described in this tutorial: https://doc.qt.io/QtForDeviceCreation/qtee-custom-embedded-linux-image.html But the b2qt-embedded-qt5-image-1.0-r0 do_rootfs function is failing for the command bitbake b2qt-embedded-qt5-image Apr 24 21:27:13 The error is as follows: Apr 24 21:28:52 * check_data_file_clashes: Package v86d wants to install file /home/ian/dev/yocto-rpi/build-raspberrypi4/tmp/work/qemux86-poky-linux/b2qt-embdedded-qt5-image/1.0-r0/rootfs/etc/modprobe.d/uvesafb.confBut that file is already provided by package * kernel-module-uvesafb-5.0.19-yocto-standard Apr 24 21:28:56 Hi! I'm trying to generate signed ipk files and allow opkg to verify the signature. I looked at the opkg recipe and figured that I needed to add PACKAGECONFIG += "gpg" to a bbappend.. Apr 24 21:29:45 khem: Hi! I'm trying to get lldb-server into the target, what do I need to activate in the meta-clang layer to get it? Apr 24 21:30:32 but when I do that I get "ERROR: Nothing RPROVIDES 'nativesdk-gnupg'" along with a message saying that nativesdk-gnupg is unbuildable, removing Apr 24 21:32:08 fullstop: it looks like it's missing `nativesdk` inside the BBCLASSEXTEND variable. Apr 24 21:32:22 Maybe there is a reason why it's not there? Apr 24 21:32:29 the gnupg recipe? Apr 24 21:32:33 yes. Apr 24 21:32:36 odd Apr 24 21:33:28 it is there in the master branch.. Apr 24 21:33:43 ha, I'm using zeus. Apr 24 21:34:03 It is not there in zeus.. so it was added at some point. Apr 24 21:34:10 Indeed. Apr 24 21:34:32 https://github.com/madisongh/openembedded-core/commit/e935cba0122a93df611c9a846c16b7841b715fd8#diff-55efebd68b94c80044d12e03ff612c50 Apr 24 21:35:35 do I need to bbappend all of those recipes? dang. Apr 24 21:36:03 Start with the one you need. Apr 24 21:36:34 Haaa man powershell... why! I can't click on links :( Apr 24 21:39:23 roussinm: all needed to be appended. Apr 24 22:22:13 roussinm: I guess add lldb to IMAGE_INSTALL Apr 24 22:35:05 halifax: its a file clash. I wonder why v86d is trying to install uvesafb.conf Apr 24 22:35:34 @khem: I also don't know. Apr 24 22:35:51 Can I rerun all tasks related to v86d? Apr 24 22:36:10 perhaps you can check recipe and see if its doing anything quirky in do_install Apr 24 22:36:21 also check if there are some bbappends Apr 24 22:39:58 halifax: why are you using b2qt Apr 24 22:47:22 I'm trying to develop with Qt on my Raspberry Pi Apr 24 22:51:23 I'm trying to develop an embedded system. Is there a better way? Apr 24 22:53:21 You'll need to give a lot more detail. You haven't said enoughf or us to answer. Apr 24 22:53:38 "develop an embedded system" is extremely vague Apr 24 22:58:46 I'm trying to develop a mini touch desktop interface that runs on Yocto. Kind of like a tablet OS. Wanted to use the PC as the host dev system and deploy to Raspberry Pi. I was thinking Qt + Qt Creator Apr 24 23:09:09 hi. Im new in yocto but I like it :) I have a problem! I think I have misunderstand. in our company we have a powerPC chip that we have yocto package ready for it Apr 24 23:09:29 we build image and now our board boot from nfs Apr 24 23:10:00 our boards load kernel and rootfs from nfs server Apr 24 23:10:59 after boot up I see in "du" that I have only 12 MB for / and some other partition with 100 MB Apr 24 23:11:16 I want to know how I can change ram partition ?? Apr 24 23:11:23 sorrry for poor English Apr 24 23:12:33 I want to have 50 MB for / for example!! but I dont know how !! Apr 24 23:19:42 Moh3N: welcome and glad you like it Apr 24 23:19:56 Moh3N: you can add extra space to your image Apr 24 23:20:36 thank you, I want some key words and road map to solve my problem, thanks Apr 24 23:21:29 Is there a way I can remove and rerun all the tasks for v86d? Apr 24 23:21:51 Moh3N: in conf/local.conf add something like MAGE_ROOTFS_EXTRA_SPACE_append = " + 64000" Apr 24 23:22:08 Moh3N:that should add 64M to your rootfs Apr 24 23:22:50 halifax: bitbake -ccleansstate v86d Apr 24 23:23:38 thanks a lot :) and how I can decrease some MB from Other partition and increase another ?? in yocto Apr 24 23:33:56 bitbake -ccleansstate v86d ran successfully, but I'm still getting the same error when I run bitbake b2qt-embedded-qt5-image after that. When I try to run bitbake -ccleansstate kernel-module-uvesafb-5.0.19-yocto-standard, it says ERROR: Nothing PROVIDES 'kernel-module-uvesafb-5.0.19-yocto-standard'. Close matches: linux-yocto RPROVIDES Apr 24 23:33:57 'kernel-module-uvesafb-5.0.19-yocto-standard' Apr 24 23:37:01 Should I be running bitbake -ccleansstate linux-yocto? Apr 24 23:48:47 moto-timo: Apr 24 23:49:48 halifax: no, you should first delete it via do_install in one of the recipes Apr 24 23:50:31 I should delete v86d and not kernel-module-uvesafb-5.0.19-yocto-standard, right? The latter sounds important. Apr 24 23:51:18 perhaps yeah, Apr 24 23:51:20 hmmm.... "v86d provides a backend for kernel drivers that need to execute x86 BIOS code. The code is executed in a controlled environment and the results are passed back to the kernel via the netlink interface. Apr 24 23:51:25 that will be easier Apr 24 23:54:08 but I think kernel module should not be providing it either Apr 24 23:54:38 so perhaps compare uvesafb.conf from both packages and see which one is appropriate for your case Apr 24 23:55:00 btw. what target are you building for Apr 24 23:55:44 MACHINE=raspberrypi4 Apr 24 23:56:01 hmm then why is it using linux-yocto Apr 24 23:56:16 I have no idea. I'm looking for the recipe Apr 24 23:56:58 halifax: are you open to use some other distro then there are others ways to get QT5 images Apr 24 23:57:11 Sure Apr 25 00:48:53 khem: pocket dial or trying to call my attention to the interaction? **** ENDING LOGGING AT Sat Apr 25 02:59:57 2020