**** BEGIN LOGGING AT Fri Aug 23 03:00:40 2019 Aug 23 06:10:13 mischief: A friend did, he said that it worked quite well after identifying some problematic recipes and adding them to the blacklist. Aug 23 07:09:26 erbo: at work with ubuntu it was fine today but i had problems at home on debian. i think it has to do with a bug in the packaged icecc version :( Aug 23 08:46:51 hi! i'm wondering what's the best way to debug "The metadata is not deterministic" errors? i cannot really use bitbake-diffsigs because there is only one `sigdata` file Aug 23 09:10:22 RP: yeah, it would have been helful to have you even at the BoF but, hopefully you'll make it to ELCE Aug 23 09:13:57 aehs29: that is the plan Aug 23 09:55:50 New news from stackoverflow: Removing a sub package from a main package in Yocto Aug 23 09:57:39 runqemu wants a qemuboot.conf. How to generate qemuboot.conf? Aug 23 10:05:05 hi, im getting arm-oe-linux-gnueabi-gcc: error: unrecognized command line option '-fstack-clash-protection'; did you mean '-fstack-protector'? on geoclue Aug 23 10:25:54 New news from stackoverflow: Where can I find the mapping of SAMA5D27-SOM1-EK1 devices and it's GPIOS? Aug 23 10:39:12 aehs29, how is ELC? I've heard complaints about all the cloud keynotes :) Aug 23 10:39:16 urg Aug 23 10:52:33 Crofton: what cloud keynotes? Aug 23 10:53:17 sponsor keynotes Aug 23 11:15:32 hello everyone Aug 23 11:15:48 i might have a very stupid question regarding the building process Aug 23 11:16:43 i built two bzImages: bzImage--5.0.19+git0+31de88e51d_00638cdd8f-r0-i... and bzImage-initramfs--5.0.19+git0+31 Aug 23 11:16:59 by default bzImage make a symlink to the first one Aug 23 11:17:21 and in image bzImage is put Aug 23 11:17:50 how can I say to symlink bzImage to bzImage-initramfs--5.0..... so it will be put into the final image? Aug 23 11:17:54 thanks in advance :) Aug 23 11:22:36 i think it's coming from meta-intel layer Aug 23 13:56:26 New news from stackoverflow: I can't find the problem in My C program for SAMA5D27 board Aug 23 14:13:37 how to make inherit and includes in recipes/bbclasses specific to target build only, e.g. class-target? Aug 23 15:00:58 hello folks Aug 23 15:01:38 in the yocto manual, it says that PACKAGES of a package is prepopulated with ${PN}, ${PN}-dev etc. and everything that's not put into a package explicitly is put into ${PN} Aug 23 15:02:08 I've created a recipe and an do_install. However, yocto complains that all my files are not packaged into any packages. why's that? Aug 23 15:03:09 ahh wait. that's not quite correct. FILES_${PN} is explicitly specified to look below bindir, etc. but not below /foobar Aug 23 15:11:36 litb: Correct. Yocto expects that you adhere to a directory layout that follows the filesystem hierarchy standard. If you don't, you'll have to write packaging rules yourself. Aug 23 15:13:12 neverpanic, we decided that we don't want a packaging system on the target, because our firmware is basically an "/opt-style" software with its own hierarchy Aug 23 15:13:25 with the yocto distribution only providing the runtime environment Aug 23 15:14:04 so we plan to update our yocto target devices with rsync (for individual developers, they can still use devtool) Aug 23 15:14:14 otherwise, we would have to mess with the packages on the target device Aug 23 16:06:31 erbo: do you know if it's possible to get yocto's icecc support to work on a non-native arch remote system? Aug 23 17:37:06 no readelf recipe? Aug 23 17:41:28 readelf isn't a project Aug 23 17:41:31 it's part of binutils Aug 23 17:41:41 there is are two readelfs Aug 23 17:41:46 binutils and elfutils Aug 23 17:41:56 but correct, it's not standalone Aug 23 17:52:08 there is nothing in the yocto cross-compile process which would throw out the -g option, is there? Aug 23 17:52:38 can i check my exe with readelf to see if the debug info is there? Aug 23 17:53:05 install the -dbg packages if you need debug symbols. we split them out to save space normally Aug 23 17:53:14 aha! Aug 23 17:53:18 absolutely the system plays with the option(s). Debug is always split, unless you disable stripping and splitting of dbg symbols Aug 23 17:53:20 berry good! Aug 23 17:53:32 In almost all cases, there is no reason to have them as one, as GDB can connect the split to the executable. Aug 23 17:56:25 so when i install XYZ-dbg, does that overwrite the regular XYZ in /usr/bin with the debug version? Aug 23 17:57:15 readelf --sections `which XYZ` still lists no debug info after installing XYZ-dbg Aug 23 17:58:17 the debug items are merged by gdb at gdb runtime.. NOT at package install time Aug 23 17:58:43 i am using valgrind, not gdb Aug 23 17:58:53 look at the contents of the -dbg package to see where they are.. Aug 23 17:59:04 valgrind, some versions, can deal with split symbols.. Aug 23 17:59:33 if the version and arch you are using doesn't in valgrind, then you would have to manually merge them back with objcopy.. but I don't have instructions to do that Aug 23 18:00:39 i'm using 3.12.0 Aug 23 18:01:29 are you talking aabout the --extra-debuginfo-path=path option? Aug 23 18:01:40 yes.. that is automatic in gdb Aug 23 18:02:04 how do i find the files from that package? (rpm) Aug 23 18:02:34 nm Aug 23 18:02:39 rpm -ql pkg Aug 23 18:02:40 / Aug 23 18:02:42 ? Aug 23 18:04:16 typically they are in a subdirectory called '.debug'. For instance, bin/bash look in bin/.debug/bash Aug 23 18:04:29 this is standard Debian behavior, but it can be changed Aug 23 18:34:29 Excellent timing RP. I was just about to ask if you had anything to start. :) Aug 23 18:40:14 fray: after installing server-6300-dbg, i have a single file, /usr/bin/.debug/server-6300, and a whole directory structure under /usr/src/debug/server-6300 Aug 23 18:40:35 which one of these paths should be used in the --extra-debuginfo-path=path option? Aug 23 18:40:38 yes.. debug symbols under .debug and user usr/src is all of the associaed (referenced) source code Aug 23 18:40:46 i've tried numerate variations and nothing seems to work Aug 23 18:40:51 numerous Aug 23 18:40:57 you'll have to look at the valgrind docs.. I would assume the .debug, but I don't know Aug 23 18:42:35 you shouldn't nee to pass anything, we set up debuglink in the binaries to point to the symbols Aug 23 18:44:35 kergoth: this command: root@imx6ul-var-dart:~# valgrind --leak-check=full --leak-resolution=high --show-leak-kinds=all --track-origins=yes `which server-6300` -nort Aug 23 18:44:44 produces this output at theend: Aug 23 18:45:01 https://paste.fedoraproject.org/paste/3i8B3dQgUVSbsxvFmY017w Aug 23 18:45:40 so no debug info. :( Aug 23 18:46:31 in fact it has displayed similar no matter what path i specify for the --extra-debuginfo-path=path Aug 23 18:47:13 including /usr/bin/.debug, /usr/bin/.debug/server-630, /usr/src/debug/, /usr/src/debug/server-6300, ... Aug 23 18:47:46 wall -> | <- head Aug 23 18:48:06 i desparately need this debug info Aug 23 18:48:48 read the valgrind docs on how to deal with split debug symbols.. this split stuff is standard.. the YP stuff is setup verify similar to debian, but other then path is also the same as RH/CentOS debug packages Aug 23 18:49:33 fray: i've read/reread the doc on the --extra-debuginfo-path - is there somewhere else to read? Aug 23 18:50:05 don't know but I would expect some sort of tutorial or walk through somewhere on this.. I don't use valgrind like that very often.. Aug 23 18:50:16 usually when I do it's on my development host, not hte target system Aug 23 18:50:32 i'm a valgrind extra-debuginfo-path virgin myself Aug 23 18:51:42 kergoth: what say you? Aug 23 18:51:47 question: Aug 23 18:52:10 if i've installed the XYZ-dbg package, should i uninstall the XYZ package? Aug 23 18:52:17 btw, I'm using smart package manager Aug 23 18:53:51 i'm thinking no. you're saying you need both the main exe and the dbg info right? Aug 23 18:57:17 New news from stackoverflow: How to add a Linux kernel configuration to a YOCTO Linux OS image? Aug 23 19:27:21 New news from stackoverflow: How to add a Linux kernel configuration to a YOCTO Linux OS image? [on hold] **** ENDING LOGGING AT Sat Aug 24 02:59:57 2019