**** BEGIN LOGGING AT Wed Jul 12 03:00:04 2017 Jul 12 09:10:32 JaMa: you mentioned imagemagick doesn't match python-wand a few weeks ago, did that get resolved or shoudl I look into it> Jul 12 09:10:35 ? Jul 12 09:28:07 koen: I've downgraded imagemagick in our layer that fixes python-wand for me, but it's still broken for other users Jul 12 21:26:16 khem, master of today and your 3 patches: klibc fails to build with glibc Jul 12 21:26:54 here it is: make: *** empty string invalid as file name. Stop. Jul 12 21:28:03 ant_home: which machine ? Jul 12 21:28:13 btw I see JaMa uilds armv5te while my devices default now to armvce. Default distro. Why? Jul 12 21:28:26 here it is c7x0 Jul 12 21:28:54 sorry: armv5te vs. armv5e Jul 12 21:29:08 seems I lost thumbs on the way... Jul 12 21:29:40 ant_home: I think your DEFAULTTUNE disables thumb Jul 12 21:29:46 * ant_home typing in the dark: mosquitos BlitzKrieg :/ Jul 12 21:30:14 it must have been changed long ago, BSP layer did not change Jul 12 21:30:59 I am looking at the los now Jul 12 21:31:29 I disable thumb when building klibc unless machine enables it Jul 12 21:32:05 yes, I'll check this other issue later Jul 12 21:32:16 no changes to the meta-handheld machines Jul 12 21:34:00 ant_home: tune-xscale.inc says DEFAULTTUNE ?= "armv5te" Jul 12 21:34:04 hmm Jul 12 21:35:14 https://pastebin.com/sejm6pe6 Jul 12 21:35:54 khem, it is long that it lost thumb, is strange JaMa got it back Jul 12 21:36:41 maybe I missed one big change to the tune files... Jul 12 21:38:36 ant_home: can you try meta-initramfs/recipes-devtools/klibc/klibc.inc Jul 12 21:38:49 change KLIBCTHUMB = "${@['', 'CONFIG_KLIBC_THUMB=y'][(d.getVar('ARM_INSTRUCTION_SET') == 'thumb')]}" Jul 12 21:39:15 to KLIBCTHUMB = "${@['CONFIG_KLIBC_THUMB=n', 'CONFIG_KLIBC_THUMB=y'][(d.getVar('ARM_INSTRUCTION_SET') == 'thumb')]}" Jul 12 21:42:37 khem: it builds now Jul 12 21:43:17 ok Jul 12 21:43:30 klibc-static-utils as well Jul 12 21:43:32 i will send a v3 Jul 12 21:43:34 does anybody know if armv7 has write combining? Jul 12 21:43:56 khem, still armv5e ofc Jul 12 21:44:35 I should see CONFIG_KLIBC_THUMB=y KLIBCOPTFLAGS= -march=armv5te -mthumb Jul 12 21:44:42 as it was Jul 12 21:44:55 but again, it is not your patchset Jul 12 21:51:01 khem, the machines do require conf/machine/include/tune-xscale.inc Jul 12 21:52:11 then why does it not default to DEFAULTTUNE ?= "armv5te" Jul 12 21:52:14 hm... Jul 12 21:58:35 it is indeed set like that but... Jul 12 21:58:36 https://pastebin.com/8ZbGZVch Jul 12 22:03:06 what does TUNE_FEATURES have Jul 12 22:06:05 khem, TUNE_FEATURES = "arm armv5 thumb dsp" Jul 12 22:06:47 ok Jul 12 22:07:11 khem, grepping I found in glibc-ld.inc Jul 12 22:07:18 I wonder if I should compile klibc in thumb mode if soc supports it Jul 12 22:07:46 original_tune=d.getVar("DEFAULTTUNE_MULTILIB_ORIGINAL") Jul 12 22:07:53 this var seems never set Jul 12 22:08:04 just quick grep Jul 12 22:08:13 does new klibc work Jul 12 22:08:30 I am charging the device Jul 12 22:08:37 I'll test the utils Jul 12 22:29:43 khem, static binaries ar Jul 12 22:29:47 e ok Jul 12 22:30:58 yeay Jul 12 22:31:44 ub-utils-klibc builds also fine Jul 12 22:40:14 khem, tested ok mtdinfo and ubinfo both built klibc-static. Jul 12 22:41:59 ant_home: ok Jul 12 22:42:05 I sent the patch to ml Jul 12 22:42:12 thanks Jul 12 22:43:02 next test musl and armv4 (no thumb) **** ENDING LOGGING AT Thu Jul 13 03:00:02 2017