**** BEGIN LOGGING AT Mon Feb 19 03:00:02 2018 Feb 19 07:33:45 good morning Feb 19 11:55:01 New news from stackoverflow: Compile Yocto project Feb 19 13:03:57 hi #yocto, I search a page with the history of all releases (with dates and main changes) is this somewehere documented? Feb 19 13:06:43 silviof: look here: https://wiki.yoctoproject.org/wiki/Releases Feb 19 13:06:47 silviof: Thanks silviof Feb 19 13:07:46 i hope this was for the record, and not actually talking to yourself :P Feb 19 16:00:49 hi everyone. i've got a bit of a problem with the opencv recipe in meta-oe, rocko Feb 19 16:01:14 for your device we need python-opencv (python2) as well as some libopencv-*-dev packages Feb 19 16:01:57 but it seems that when adding `python2` to the packageconfig so python-opencv exists, python3-opencv doesn't work anymore. at the same time, libopencv-*-dev packages seem to all trigger a dependency on python3-opencv Feb 19 16:02:05 so the build fails when i use both Feb 19 16:31:31 i have a yocto image i access via serial and/or ssh. i noticed that on the terminal all kind of control sequences are printed out instead of being interpreted Feb 19 16:31:36 which is very annoying Feb 19 16:31:44 perf report for example Feb 19 16:31:49 any idea how to fix this? Feb 19 16:33:45 maybe change serial protocol settings ? Feb 19 16:36:29 no Feb 19 16:36:32 happens also via ssh Feb 19 16:41:22 Control sequence like keyboard arrows & home and end keys? Feb 19 17:14:51 khem: From a few days ago you metioned glibc problems with FC27 & morty. Would that be related to: sysroots-uninative/x86_64-linux/lib/libc.so.6: version `GLIBC_2.25' not found (required by .../libpython2.7.so.1.0) Feb 19 17:53:14 JPEWhacker: its mixing libc versions on your host. when did you reboot the system last Feb 19 17:55:11 another issue could be that glibc in uninative is older than glibc on f27 Feb 19 17:55:40 you might have to regenerate uninative tarball with latest glibc from oe-core Feb 19 18:48:31 khem: Recently... perhaps there was a system update since then. I will try again. Feb 19 19:04:12 * armpit hmm, rocko failed with 4.12.20 on arm64 Feb 19 19:27:51 Does anyone know of some published steps for getting a device tree to load? I see a u-boot log message indicating it loaded the correct device tree file name from my boot partition, but when I check /proc/device-tree, it's incorrect. Feb 19 19:52:26 * armpit cool, reproduce morty ruby build issue Feb 19 19:54:20 armpit: Are you getting the Ruby build issue with the segfault also? Feb 19 20:05:01 JPEWhacker, on the AB I can not tell. my local home system is ( ubuntu 17) Feb 19 20:05:14 JPEWhacker: about the control sequences. the "text ui" shown by "perf report" is for example broken Feb 19 20:05:28 does have a segfault Arm64 multilib Feb 19 20:05:37 [[31m 5.24%[[m find [kernel.kallsyms] [k] ext4_iget Feb 19 20:05:42 contains bits like that Feb 19 20:05:51 [[m Feb 19 20:06:12 and i can't properly cursor navigate Feb 19 20:06:47 fmeerkoetter: I may have something for you.... j/s Feb 19 20:14:38 fmeerkoetter: Hmm.... I'm not sure this will fix the perf report, but this fixes the arrow keys in the prompt for me: http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=jpew/master&id=727e176c427a1cfeeaf3ce6f65c75c1492b50e01 Feb 19 20:15:05 The perf one looks like color codes, which probably means some terminal setting Feb 19 20:15:56 I did not know segfaults where color coded. Red real bad, yellow some what bad Feb 19 20:17:12 armpit: Where is that? Feb 19 20:28:44 JPEWhacker: thanks Feb 19 20:29:01 i'll give it a spin Feb 19 21:05:09 * armpit cool something in ruby 2.4.3 fixed the segfaul Feb 19 21:16:46 halstead, ping.. is the old ab stable enough to use? Feb 19 21:18:56 armpit: re odroid, I am re-adding recipes for hardkernel forks of u-boot and kernel, there simply are too many features not working upstream yet Feb 19 21:31:21 armpit, You can give it a try if you want but it is running the new build code so it's quite different from the .io cluster. Feb 19 21:37:53 armpit: i wouldn't expect a green build. use .io? Feb 19 21:53:03 halstead, rburton k Feb 19 21:53:06 khem, k Feb 19 21:53:45 what's the best way to have a tarball created of some non-rootfs artifacts from DEPLOY_DIR on every build? Feb 19 21:54:30 denix: Collecting items from different recipes, or from the same recipe? Feb 19 21:57:02 JPEWhacker: different recipes Feb 19 21:57:20 denix: I'm not sure then. Sorry Feb 19 22:27:07 New news from stackoverflow: Cannot satisfy the following dependencies for packagegroup-core-boot Feb 19 23:45:45 zeddii: around? Feb 19 23:45:54 armpit: I assume you saw the arm64 failures? Feb 19 23:50:04 yes Feb 19 23:50:42 ran it 2x.. to eliminate build weirdness Feb 19 23:50:55 4.9 kernel changes are in Feb 19 23:51:07 I will but it after some oympics Feb 19 23:51:15 s/but/bug/ Feb 19 23:52:13 armpit: am I safe to merge the other bits in stable minus the kernel? It is the kernel update causing that? Feb 19 23:52:46 correct Feb 19 23:53:06 just started morty to see if it fixes ruby build issues Feb 19 23:55:22 armpit: I've told QA to ignore 2.4.2 rc1 and wait for rc2. The build blocker is therefore a pain :( Feb 20 00:26:56 armpit: might want to kill, fix and restart that! Feb 20 00:27:10 (ruby checksum issue) Feb 20 00:27:14 * RP -> Zzzz Feb 20 00:27:22 aah Feb 20 00:27:32 * armpit dang Feb 20 00:38:23 * armpit fires up rlocal ocko-stable build Feb 20 00:38:44 * armpit forgot to push change to recipe **** ENDING LOGGING AT Tue Feb 20 03:00:02 2018