**** BEGIN LOGGING AT Tue Oct 23 02:59:59 2018 Oct 23 03:05:14 New news from stackoverflow: Using PREMIRRORS in Bitbake configuration Oct 23 06:41:48 hi, what does it means exactly " oe_runmake failed " ? Oct 23 09:05:31 Hi, i'm looking for some help with meta-qt5. I'd like to change default libs path (/usr/lib) to custom (/opt/lib) on the target. I've been trying for 2 days and still have problems with building (yocto-sumo). Oct 23 09:14:00 kasper150: But... why? :p Oct 23 09:21:06 yeah, that would also be my first question... Oct 23 09:29:28 hi, building a C application, library includes (.h) are not found while building. I see the headers in the temp build sysroot, could you point me to some docs to solve this ? Oct 23 09:33:26 lo all, need some help with debugging a process hanging up systemd Oct 23 09:35:31 jofr boucman_work I use a kernel with bundled initramfs and overlayfs. I'd like to add qtwebengine but the size of initramfs is too big. Thats why :D Oct 23 09:46:21 I tried to build latest openjdk-8 (V 162b12) . It successfully compiled for armv7 processor, But when I run java on imx6 module (Toradex) , it give me core dump Error. Oct 23 09:46:35 I used sumo branch Oct 23 09:49:57 anyone have any idea on this ?? Oct 23 09:59:45 any help on this issue? Oct 23 10:07:43 actually i created linux os with yocto latest (sumo), and clone letest meta-java banch and truing to build openjdk-8 . it compiled successfully , when i run the java on hardware (imx6 module (Toradex)) it casue core dump error Oct 23 10:08:09 any solution friends?? Oct 23 10:13:53 hello Oct 23 11:24:49 can anyone help me with this: i want to install meta-ros to my image that is going to be flashed on a jetson tx2 Oct 23 11:25:30 where can i tell bitbake to get the packagegroup-ros-comm into the image Oct 23 11:25:52 magicmoon: just add it in the IMAGE_INSTALL of your image recipe Oct 23 11:26:15 magicmoon: if you do not have an image recipe, step #1 of any yocto project based thing: create an image recipe Oct 23 11:26:44 i do have an image recipe Oct 23 11:26:52 well then add it there. Oct 23 11:27:21 its image-xfce.bb Oct 23 11:27:45 then i add IMAGE_INSTALL_append =+ "packagegroup-ros-comm" Oct 23 11:27:50 magicmoon: that sounds wrong. Oct 23 11:28:07 += Oct 23 11:28:08 magicmoon: sounds like you are modifying some image in an upstream layer Oct 23 11:28:32 yes i added it to an existing image Oct 23 11:29:15 bad idea. better always have a layer of your own where you do stuff. imagine you need to update said layer for an update or bugifx. what happens to your modifications? Oct 23 11:30:09 i will have to add it again Oct 23 11:30:15 :( Oct 23 11:30:18 hmm Oct 23 11:30:19 sse, thats why it is a bad idea. Oct 23 11:30:45 well as u can see i am a noob Oct 23 11:31:09 actually i got this yocto build and just want to add the meta-ros to the build Oct 23 11:31:19 in general, when ever you are modifying something in a layer that you downloaded (and that you do not maintain yourself), it is almost certainly wrong (exception, you are preparing a patch to submit) Oct 23 11:31:35 magicmoon: "just want to" often goes astray, sorry. Oct 23 11:32:01 I get the error "nothing provides /bin/awk", when building kernel-devsrc. Any ideas how to solve this? Oct 23 11:32:15 magicmoon: so the appraoch should be to add meta-ros to your build, and add a meta-magicmoon to hold your personal stuff Oct 23 11:32:43 I've managed to build a raspberry pi image with docker... but I'm pretty sure I'm missing something pretty big. Should I be making a recipe instead of just modifying layers and local.conf? Oct 23 11:33:10 submux: depends on what you want to do. Oct 23 11:34:34 LetoThe2nd, I am hoping to make an image that I can use for managing centrally. I have written some kernel modules and also want to configure SSH keys in the image. Oct 23 11:34:43 i will flash the device now with the updated image Oct 23 11:34:54 i'll be back in a few min Oct 23 11:35:49 submux: i don't get the point. "an image i can use for managing centrally" Oct 23 11:36:14 so what is it that you want to do? add your drivers? add some software? rebuild it with alternating configurations? Oct 23 11:36:17 LetoThe2nd, I'm planning on doing something like ResinOS if you know that platform Oct 23 11:36:43 submux: ah Oct 23 11:36:45 And also have some form of CI/CD in place so I can write tests against it Oct 23 11:37:16 submux: well then why not just use their stuff (and fork it if you really need substantial modifications) Oct 23 11:38:39 LetoThe2nd, I agree that would likely be the best solution, but for the moment, I know Docker quite well but I don't know Resin.IO. Also, their stuff really works very well against their cloud platform, and I can't really use that Oct 23 11:39:14 submux: hum well ... i just sense that you are basically still working the steep learning curve of openembedded technology. Oct 23 11:39:52 submux: you'd need one or more layers to hold your stuff. you'd need recipes for everything you want to add, you'd have images for things to biuld Oct 23 11:39:59 plus, extra machines etc.. Oct 23 11:40:26 And to do anything meaningful with that, I need to better understand openembedded tech as you said. It'll be a steep learning curve, but I believe it is worth the investment. Yocto is some pretty impressive technology from what I've experienced thus far Oct 23 11:40:41 if the resin.io is too much for you maybe also look at oryx (i think its called like that) from tagon labs. its basicall the container tech without cloud foo Oct 23 11:40:49 anyways, lünch. Oct 23 11:40:55 Thanks for the info! Oct 23 11:53:35 i created linux os with yocto latest (sumo), and clone letest meta-java banch and truing to build openjdk-8 . it compiled successfully , when i run the java on hardware (imx6 module (Toradex)) it casue core dump error Oct 23 11:53:51 can anyone help me on this? Oct 23 11:59:18 Hi guys.. How to add the 'u-boot-fw-utils' package to the image? I have added PREFERRED_PROVIDER_u-boot-fw-utils = "u-boot-fw-utils" and EXTRA_IMAGEDEPENDS += "u-boot u-boot-fw-utils ..." Oct 23 12:00:10 But I did not see the fw_setent files in my rootfs Oct 23 12:00:25 s/fw_setent/fw_setenv Oct 23 12:01:19 I see that this file is in working directory Oct 23 12:02:05 but it does not installs to the rootfs Oct 23 12:10:00 kuzulis: EXTRA_IMAGEDEPENDS: A list of recipes to build that do not provide packages for installing into the root filesystem. Oct 23 12:13:01 uglyoldbob: Do I need to add this to RDEPENDS_${PN} ? e.g. to my packagegroup-xx.bb? Oct 23 12:13:42 kuzulis: that should work Oct 23 12:13:52 ok, many thanks Oct 23 12:33:21 rather, IMAGE_INSTALL Oct 23 12:33:25 kuzulis: ^^^^^ Oct 23 12:36:19 Ohhhh.. I already added it to RDEPENDS... let's be there ))) Oct 23 12:37:05 kuzulis: i cannot properly argument if RDEPENDS works properly for images, but if it does not, don't be surprised. Oct 23 12:37:31 kuzulis: the general idea is like this: an image specifies what packages to install through IMAGE_INSTALL Oct 23 12:38:15 kuzulis: packages (respectively their recipes) specify what need for being built (DEPENDS) and to work at runtime (RDEPENDS) Oct 23 12:38:33 kuzulis: where you actually only need IMAGE_INSTALL and DEPENDS about 90% of the time Oct 23 12:39:16 Ahh.. ok, thanks, I will use IMAGE_INSTALL then Oct 23 12:39:35 magic Oct 23 12:40:10 no magic involved. we usually hide the arcane stuff at completely different locations :) Oct 23 12:40:38 thx for yours, times, guys Oct 23 12:41:45 np Oct 23 12:42:29 just alsways remember: if you ask here and get no aswer, then it means that either a) nobody knows or b) nobody has time to spare. Oct 23 12:42:41 )) Oct 23 12:42:42 if sombody answers, then ... well, thats the point of a support channel Oct 23 12:42:43 ok Oct 23 13:24:23 hi again Oct 23 13:34:31 Hi, guys! Oct 23 13:35:34 I have an answer. Can I add qemu binaries to image? The goal is using qemu on target machine. Oct 23 13:36:17 I've found meta-virtualization, but that's not what I am searching for. Oct 23 13:36:24 acrap try meta-virtualization Oct 23 13:37:35 submux: I've added virtualization to DISTRO_FEATURES, but that doesn't add qemu binaries to rootfs Oct 23 13:39:03 acrap: erm, have you tried just doing IMAGE_INSTALL += "qemu" ? Oct 23 13:40:11 LetoThe2nd: yep, I've tried it (local.conf), but it looks like it just ignored. No errors, no qemu in rootfs Oct 23 13:40:19 i mean, qemu has a boatload of options to tune, but basically looking at the recipes suggest it should be installable like any other thing Oct 23 13:41:27 hello Oct 23 13:41:49 did anyone here had success with integrating meta-ros into his yocto project? Oct 23 13:42:35 acrap: for a quick hack test (to be poured into proper code later) you can just do BBCLASSEXTEND =+ "native nativesdk" in meta/recipes-devtools/qemu/qemu.inc Oct 23 13:42:47 acrap: (instread of the '=') thats already there Oct 23 13:43:15 magicmoon: well did you already follow the steps i gave you? create your layer to contain your steuff, add an image recipe in there? Oct 23 13:44:39 magicmoon: or are you stuk even earlier? Oct 23 13:46:05 LetoThe2nd: seems like I used a wrong local.conf (too much build directories...). It is compiling now. Oct 23 13:47:19 acrap: local.confusion Oct 23 13:47:35 (i hereby declare that to be the official #yocto pun) Oct 23 13:48:01 LOL Oct 23 13:50:46 acrap... good to see you got it, I was looking and just figured it out :) Oct 23 13:51:07 LettoThe2nd Oct 23 13:51:13 i did Oct 23 13:51:26 but its still not working Oct 23 13:51:51 building a CPP app by yocto, for ARM, i get full of " #error "Unknown __WORDSIZE detected"" , what could it be ? Oct 23 13:53:59 magicmoon: ok, now try to be precise. what is "not working" Oct 23 14:01:19 ok in the image i get by bitbake when i look into it there is under /opt a ros folder Oct 23 14:02:01 when i flash this image to the target this doesn't get into the opt folder on the target Oct 23 14:02:35 magicmoon: does your board have a mount overlaying /opt, maybe? Oct 23 14:03:15 hmm can u tell me how i can check that? Oct 23 14:03:29 magicmoon: on your board, run "mount" Oct 23 14:03:48 if in doubt, copy-paste it to a pastebin and share the resulting link for us to have a alook Oct 23 14:07:22 https://pastebin.com/GaxgmQW7 Oct 23 14:07:30 i just typed mount Oct 23 14:07:38 and the the result is at pastebin Oct 23 14:07:55 magicmoon: line 22, clearly an overlay mount Oct 23 14:08:42 magicmoon: so something is totally messing up your board, the numbering suggests that there are almost 20 partitions in mmc block device Oct 23 14:09:40 i seriously suggest to yell at your supplier to provide a proper setup including documentation Oct 23 14:09:57 what kind of hardware and board is this? Oct 23 14:14:27 this is an ecu with the nvidia jetson tx2 som Oct 23 14:17:22 the board is up and running but i don't see the ros stuff on the system and i am wondering why Oct 23 14:17:37 magicmoon: seriously, go yell at whoever gave it to you. Oct 23 14:18:04 yeah ... well ... u know ... yelling will not help me to solve this Oct 23 14:18:45 it sounds very much like you are an intern or such that was just handed the gear and are supposed to get something working, but you are lost in so many ways that just trying to beat it into shape here forever will not going to solve it either Oct 23 14:19:31 well u can definatly say that ... i have to solve it so i can push out ros messages from the system Oct 23 14:19:58 an ecu is pretty specific hardware, and the nvidia stuff is not exactly a prime example for good board support either. this means, either tell your supervisor that you need seirous assistance in real life (instead of just IRC) or that this thing will not work Oct 23 14:22:49 so you are actually fighting a couple of battles at once: 1) you seem to be quite a linux novice 2) probably even more an embedded novice 3) you have hardware nobody knows 4) you have a setup that is probably super specifc (for a reason or not, i don't know) 5) and for all chances, a broken board support package Oct 23 14:23:36 i mean, one can patch out at that mount. but why is it even there? somebody probably put it there for a reason. and unless you know who that was and why, just beating at the thing will do more harm than good. Oct 23 14:23:48 sorry to say, but ask for proper assistance. Oct 23 14:23:58 (off for coffee. much coffee) Oct 23 14:24:01 ok will do that Oct 23 14:24:30 thanks Oct 23 15:15:37 I'm trying to build some code using the SDK + CMake, but CMake completely ignores the CMAKE_CXX_FLAGS in my CMakeLists.txt and only uses the ones provided by the SDK. Is there some method to define those that I'm not aware of? Oct 23 15:16:03 Do I need to specify the flags in a recipe before I populate_sdk? Oct 23 15:18:33 jofr: How do you set the flags in your CMakeLists.txt? Oct 23 15:20:52 neverpanic: set(CMAKE_CXX_FLAGS "-Wno-psabi") Oct 23 15:22:28 neverpanic: When I "make", I do indeed get those psABI warnings, and a "cmake -LA " shows that the CMAKE_CXX_FLAGS is the Poky-SDK default ones: CMAKE_CXX_FLAGS:STRING= -O2 -pipe -g -feliminate-unused-debug-types Oct 23 15:26:23 I've tried deleting everything from my build-folder to make sure CMake is regenerating everything, but it doesn't matter.. Oct 23 15:27:43 But, It's not critical or anything.. It's just annoying. :-) Oct 23 19:32:50 jofr: I can only recommend to follow modern CMake practice and don't set CXX_FLAGS like you did. https://pabloariasal.github.io/2018/02/19/its-time-to-do-cmake-right/ gives a good overwiew how to do it. Oct 23 19:33:55 Having an issue with the external linaro recipe duing do_install. Has the cp -a ${TOOLCHAIN_PATH}/${ELT_TARGET_SYS}/bin/{ld*,objcopy,strip,nm,ranlib,as,ar,objdump} the {ld*,objcopy,strip,nm,ranlib,as,ar,objdump} portion is being treated as a single filename Oct 23 21:33:53 Ahh...finally realized I had dash enabled still on the system **** ENDING LOGGING AT Wed Oct 24 03:00:00 2018