Monday, 2020-01-27

*** goliath <goliath!> has quit IRC00:03
*** dev1990 <dev1990!> has joined #yocto00:08
*** FrazerClews <FrazerClews!> has quit IRC00:10
*** dev1990 <dev1990!> has quit IRC00:12
*** dev1990 <dev1990!> has joined #yocto00:13
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC00:16
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:34db:92e:2b21:713> has quit IRC01:28
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC01:34
*** dev1990_ <dev1990_!> has joined #yocto01:50
*** dev1990 <dev1990!> has quit IRC01:50
*** dev1990_ <dev1990_!> has quit IRC02:01
*** zkrx <zkrx!> has quit IRC02:03
*** zkrx <zkrx!> has joined #yocto02:09
khemRP: glibc patches are still same, but ruby patch and libucontext patch are updated02:29
khembut I can rebase on top of what you merge02:29
khemso no worrries02:29
khemI can send another round02:29
*** nerdboy <nerdboy!~sarnold@> has joined #yocto02:39
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto02:40
*** hpsy <hpsy!~hpsy@> has joined #yocto03:29
*** hpsy1 <hpsy1!~hpsy@> has quit IRC03:31
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC04:37
*** pink_vampire <pink_vampire!> has joined #yocto05:03
*** nerdboy <nerdboy!~sarnold@> has joined #yocto05:08
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto05:09
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:7cdd:d90a:ff41:24c0> has joined #yocto05:23
*** atyagi <atyagi!~ankurtyag@2407:7000:9031:dd00:c048:7736:ddd:d481> has joined #yocto05:33
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto06:10
*** sno <sno!> has quit IRC06:12
*** jobroe <jobroe!~manjaro-u@> has joined #yocto06:15
*** atyagi2 <atyagi2!~ankurtyag@> has joined #yocto06:16
*** atyagi <atyagi!~ankurtyag@2407:7000:9031:dd00:c048:7736:ddd:d481> has quit IRC06:19
*** pharaon2502 <pharaon2502!> has joined #yocto06:28
*** AndersD <AndersD!> has joined #yocto06:31
*** atyagi2 <atyagi2!~ankurtyag@> has quit IRC06:31
*** atyagi2 <atyagi2!~ankurtyag@> has joined #yocto06:31
*** atyagi2 <atyagi2!~ankurtyag@> has quit IRC06:41
*** hyper_dave <hyper_dave!~quassel@> has quit IRC06:58
*** goliath <goliath!> has joined #yocto07:03
*** hyper_dave <hyper_dave!~quassel@> has joined #yocto07:06
*** agust <agust!> has joined #yocto07:07
*** jobroe <jobroe!~manjaro-u@> has quit IRC07:09
*** sno <sno!~sno@> has joined #yocto07:10
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto07:22
*** atyagi2 <atyagi2!~ankurtyag@2407:7000:9031:dd00:c048:7736:ddd:d481> has joined #yocto07:27
*** TobSnyder <TobSnyder!> has joined #yocto07:38
*** jobroe <jobroe!~manjaro-u@> has joined #yocto07:39
*** fl0v0 <fl0v0!> has joined #yocto07:41
*** moustafa <moustafa!c533555d@> has joined #yocto07:44
*** frsc <frsc!~frsc@2003:a:e7a:6200:849b:24ee:ca9d:3215> has joined #yocto07:45
moustafahello everybody07:45
moustafaI face this error -  This application failed to start because it could not find or load the Qt platform plugin "xcb" while trying to run my UI07:45
moustafaany help ?07:45
LetoThe2ndmoustafa: did it already work? so is this a new problem, or the getting started stage?07:47
*** m1ster_r0b0t <m1ster_r0b0t!> has quit IRC07:48
LetoThe2ndmoustafa: and, di you properly build and package your application, or are you using some copy-things-here-and-there workflow?07:49
*** jeanba1 <jeanba1!~jbl@> has joined #yocto07:49
*** lucaceresoli <lucaceresoli!> has joined #yocto07:51
*** jeanba1 <jeanba1!~jbl@> has left #yocto07:52
*** yacar_ <yacar_!> has joined #yocto07:58
*** hpsy <hpsy!~hpsy@> has quit IRC07:59
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto07:59
*** pohly <pohly!> has quit IRC08:00
*** guerinoni <guerinoni!> has joined #yocto08:01
*** riz59 <riz59!c533555d@> has joined #yocto08:05
*** lfa <lfa!~lfa@> has joined #yocto08:12
erbomoustafa: Qt can be built and used with a lot of different platform plugins, depending on if you use e.g. Xorg, Wayland or just want to draw using eglfs or linuxfb. If you run the app with "-platform foo" as argument it will display a list of the available platform plugins.08:13
*** diego_r <diego_r!> has joined #yocto08:14
erbomoustafa: what machine and image are you using?08:14
*** goliath <goliath!> has quit IRC08:15
yoctiNew news from stackoverflow: how to include python pex package in yocto image <>08:20
*** warthog9 <warthog9!> has quit IRC08:23
*** alimon <alimon!alimon@gateway/shell/linaro/x-fmnlpgnvcnblroxd> has quit IRC08:23
*** sagner <sagner!> has joined #yocto08:24
*** Bunio_FH <Bunio_FH!> has joined #yocto08:32
moustafaerbo I am using minnowboard turbot with wayland protocol08:33
erbomoustafa: so you're running a wayland compositor too, like e.g. weston?08:36
*** warthog9 <warthog9!> has joined #yocto08:36
*** alimon <alimon!alimon@gateway/shell/linaro/x-fmnlpgnvcnblroxd> has joined #yocto08:36
moustafaerbo yes08:38
erbomoustafa: check if your Qt build includes any wayland backend by checking the list of plugins as I suggested earlier, and try to use that by specifiying -platform <the name of the wayland plugin>08:38
LetoThe2ndmy guess actually is that the board runs yocto, but the application comes from "somewhere"08:39
*** georgem <georgem!~georgem@> has quit IRC08:40
*** georgem <georgem!~georgem@> has joined #yocto08:40
erboLetoThe2nd: I'm not so sure, when you built qtbase you specify the default platform plugin which is xcb by default08:40
LetoThe2nderbo: just guessing :)08:40
erboSo unless you know that you should set that up properly, you will most likely need to specify the correct platform plugin when launching it08:41
moustafawhen I am using -platform eglfs or wayland it gives me the same error08:41
erbothat it couldn't find or load wayland plugin?08:43
erboor still the xcb ?08:43
moustafastill the xcb error08:43
erbobut did you get the list when you used -platform foo?08:44
erboThat sounds weird08:44
erboSo your app, is it possible it overrides Qt default argument parsing that accepts the -platform parameter?08:45
erboWhat app is it=08:45
erboMy god, I really can't produce correct english this morning08:45
*** hpsy <hpsy!~hpsy@> has joined #yocto08:47
moustafaI  found some list of Available platform plugins are: minimal, offscreen ...08:47
erboIs those all you have?08:49
moustafaAvailable platform plugins are: minimal, offscreen, vnc, wayland-egl , wayland08:49
moustafathat's all08:49
erboThen you need to look into how your Qt build is set up. If you use meta-qt5 you need to look at to see which PACKAGECONFIG options you need to enable on your platform.08:50
erboOh wait, the wayland one is actually it's own recipe.
erboSorry, didn't see you provided an updated list. So you do have wayland there08:52
riz59and wayland-egl08:52
erboBut -platform wayland produced an error about not being able to load xcb?08:53
moustafayes exactly08:53
erboTry setting QT_QPA_PLATFORM=wayland08:53
erboit's another way of specifying platform plugin08:53
moustafaok where08:55
moustafaok where i cann add this setting ?08:55
erboIt's an environment variable, if you launch if via a shell you can just put that text at the beginning on the line you use to start it08:56
erboHow do you start the app?08:56
riz59export QT_QPA_PLATFORM=wayland im assuming08:57
riz59from terminal08:57
erboyeah then you can export it before, or just do QT_QPA_PLATFORM=wayland ./my-awesome-app08:59
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:03
moustafaok thank you so much09:03
riz59That will work09:03
moustafait's working09:03
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC09:03
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto09:04
erboNice. So if you want it to be default you can create a qtbase_%.bbappend containing: QT_CONFIG_FLAGS += " -qpa wayland "09:05
*** PaowZ <PaowZ!~Vince@> has joined #yocto09:05
erboBut usually it's not that annoying to specify it when running the app09:05
moustafaaha ok09:06
moustafathanks allot09:06
*** goliath <goliath!~goliath@> has joined #yocto09:14
*** mckoan|away is now known as mckoan09:20
mckoangood morning09:20
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:48
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto09:51
*** fmo <fmo!c19ede6a@> has joined #yocto09:51
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:7cdd:d90a:ff41:24c0> has quit IRC09:54
*** pohly <pohly!> has joined #yocto10:03
*** florian_kc is now known as florian10:05
RPI don't understand the autobuilder failure :(10:15
LetoThe2ndRP: s/failure//g10:16
*** PaowZ__ <PaowZ__!~Vince@> has joined #yocto10:22
*** FrazerClews <FrazerClews!> has joined #yocto10:24
*** PaowZ <PaowZ!~Vince@> has quit IRC10:26
*** rburton <rburton!~rburton@> has joined #yocto10:30
*** kroon <kroon!~kroon@> has joined #yocto10:42
kroonEverytime I type "bitbake <myrecipe>", the recipe rebuilds from scratch. How do I debug why bitbake thinks it needs to rebuild <myrecipe> everytime ?10:44
qschulzkroon: bitbake-diffsigs -t bitbake build10:45
creichqschulz: just out of curiosity. how exactly does that command work? it seems to nee some 'sigfiles'. where do i get them?10:49
qschulzcreich: tmp/stamps10:53
qschulzbitbake-dumpsig to read the stamps10:53
creichthx :)10:54
creichsorry to bother again on that, but i keep getting 'ERROR: No sigdata files found matching busybox do_build'10:57
creichtried several other packages that are for sure listet in the tmp/stamps folder11:00
qschulzcreich: you most likely used the sstate-cache and removed the tmp dir in-between builds11:01
kroonqschulz, thanks11:01
qschulzcreich: in which case, they're not there anymore :)11:01
qschulzkroon: pleasure, I very much like this command :)11:01
creichis that cache activated by default?11:02
creichi am going to check if it's on. thank you :)11:02
*** fl0v0 <fl0v0!> has quit IRC11:06
stuom1how can I easily track down what in my image depends on python2.7?11:11
mckoandoes opkg have equivalent of dpkg-reconfigure?11:12
rburtonstuom1: PNBLACKLIST[python] = "no more python for you" and rebuild, see what breaks11:14
*** guerinoni <guerinoni!> has quit IRC11:18
*** guerinoni <guerinoni!> has joined #yocto11:19
stuom1@rburton thanks, I will try that11:21
*** JaMa <JaMa!~martin@> has joined #yocto11:22
*** riz59 <riz59!c533555d@> has quit IRC11:22
*** fl0v0 <fl0v0!> has joined #yocto11:26
*** berton <berton!~berton@> has joined #yocto11:35
stuom1python2.7 seems to be required by "perf" that is apparently required by my, but at least directly it is not. How do I now know what in my image needs perf...11:37
creicham i right when saying that signatures have to be activated manually? like 'bitbake -S XYZ'?11:38
creichi just don't see how or when i should have (accidentially) activated sstate-cache. anything i can read to understand that thing better? or any idea what i might do wrong here?11:38
*** yacar_ <yacar_!> has quit IRC11:38
stuom1nevermind my last message, im blind...11:41
*** berton <berton!~berton@> has joined #yocto11:43
*** edgar444 <edgar444!uid214381@gateway/web/> has quit IRC11:49
qschulzcreich: sstate-cache is always enabled AFAIK11:58
qschulzthat's the thing that makes rebuild way faster11:58
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC11:59
creichah, ok.. so i got your message wrong i guess. you just wanted to point out, that i might have deleted tmp at some point in time, while still having the state active...11:59
creichproably. i just deleted everything and started with a fresh build11:59
creichjust noticed, that there have been no sigfiles at all in the stamps folder and i am not sure why12:00
*** yacar_ <yacar_!> has joined #yocto12:03
qschulzcreich: like not a single one for any packagre?12:04
qschulzcreich: find -name "*sigdata*" in tmp or ANY directory that is used by Yocto and try to find where those files are.12:05
*** moustafa <moustafa!c533555d@> has quit IRC12:08
*** tgamblin <tgamblin!> has quit IRC12:09
*** sven^ <sven^!~quassel@unaffiliated/sven/x-8293843> has joined #yocto12:11
*** hamis <hamis!~irfan@> has joined #yocto12:12
*** hamis <hamis!~irfan@> has quit IRC12:19
*** tomeccles <tomeccles!~tomeccles@> has joined #yocto12:24
creichwould say they havn't been there, but not sure anymore, since i deleted the workspace12:26
creichnow in my clean build, they are where they're supposed to bw ;)12:27
creichthank you for your help and patience :)12:27
qschulzcreich: np, I also wondered why the files weren't there anymore a few days ago :) been there done that12:27
*** hamis <hamis!~irfan@> has joined #yocto12:28
*** pharaon2502 <pharaon2502!> has quit IRC12:31
*** pharaon2502 <pharaon2502!> has joined #yocto12:33
*** dev1990 <dev1990!> has joined #yocto12:39
*** tgamblin <tgamblin!~tgamblin@> has joined #yocto13:00
*** yacar_ <yacar_!> has quit IRC13:09
*** dev1990 <dev1990!> has quit IRC13:40
stuom1I'm trying to understand ptest by looking at oe-core recipes where it is enabled, and they all include file://run-ptest but I cannot find this file in any of the sources?13:48
stuom1where is it coming from?13:48
tgamblinstuom1: They're written by whomever adds the ptest. Usually they are some cut-down call to the source's "make check" or "make tests" but with some customization to make it work on our target13:51
stuom1why is the file not shipped in the sources of any of those packages13:53
rburtonits in the SRC_URI for the recipe13:55
rburtonits oe-specific so won't be upstream13:55
rburtonthe actual file is alongside the recipe in the layer13:56
rburtoneven simplier
*** AndersD <AndersD!> has quit IRC13:58
tgamblinFor comparison, a more complex one
stuom1Aaa, ok, so it is just not listed in the layer index page like patches and other files? for example pango
stuom1I looked in layer index and that file is nowhere listed in any package14:00
stuom1like patches and other stuff in SRC_URI14:00
rburtonarguably it should be in the Sources list, not sure why it isn't14:01
rburtonfile a bug for the layer index?14:01
stuom1Ok, thanks, now it is more clear :P14:01
stuom1I can file14:01
*** rburton_ <rburton_!rburton@nat/intel/x-hihjswglddlpbuwd> has joined #yocto14:08
*** rburton <rburton!~rburton@> has quit IRC14:09
*** rburton_ is now known as rburton14:09
*** pharaon2502 <pharaon2502!> has quit IRC14:11
xtronorder of layers in bblayers does matter? I think it is, but what is the rule to make the layer order, I've a layer that behaves different when order changes14:21
xtronbat thing is, it doesn't work in either way14:21
LetoThe2ndxtron: it doesn't matter if you're doing only nice things :)14:21
*** lquirion <lquirion!> has joined #yocto14:23
xtronLetoThe2nd, ok when I add meta-security in my build thing went wrong, and I can't find what wrong with the meta-security, it's an upstream layer14:23
*** kanavin <kanavin!~kanavin@> has quit IRC14:23
LetoThe2ndxtron: "think went wrong"14:24
LetoThe2ndi've never seen that bitbake message, sorry.14:24
xtronit could find tasks available in *.bbappend14:24
LetoThe2ndthat rather sounds like mixed revisions or missing layer dependencies.14:26
*** berton_ <berton_!~berton@> has joined #yocto14:26
*** RobertBerger <RobertBerger!> has joined #yocto14:27
*** berton <berton!~berton@> has quit IRC14:28
*** otavio <otavio!~otavio@debian/developer/otavio> has quit IRC14:29
*** hamis <hamis!~irfan@> has quit IRC14:29
xtronLetoThe2nd, some thing like when trying to use zeus compatible layer with sumo?14:29
*** otavio <otavio!~otavio@debian/developer/otavio> has joined #yocto14:30
LetoThe2ndxtron: that scrams for troubles, totally irrespective of bblayer order.14:32
*** frsc <frsc!~frsc@2003:a:e7a:6200:849b:24ee:ca9d:3215> has quit IRC14:34
*** frsc <frsc!~frsc@2003:a:e7a:6200:849b:24ee:ca9d:3215> has joined #yocto14:35
*** TobSnyder <TobSnyder!> has quit IRC14:39
*** frsc <frsc!~frsc@2003:a:e7a:6200:849b:24ee:ca9d:3215> has quit IRC14:41
*** frsc <frsc!~frsc@2003:a:a75:a900:2858:9ade:5ca9:3f87> has joined #yocto14:54
*** AndersD <AndersD!> has joined #yocto14:56
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:58
*** frsc <frsc!~frsc@2003:a:a75:a900:2858:9ade:5ca9:3f87> has quit IRC14:59
*** ericch <ericch!> has joined #yocto15:11
*** frsc <frsc!~frsc@2003:a:e7a:6200:849b:24ee:ca9d:3215> has joined #yocto15:11
*** bornjre <bornjre!~manjaro-b@> has joined #yocto15:15
*** sk_tandt <sk_tandt!> has joined #yocto15:24
*** sk_tandt <sk_tandt!> has quit IRC15:24
*** sk_tandt <sk_tandt!> has joined #yocto15:24
*** meego <meego!> has joined #yocto15:27
meegohow does one list the kernel's CONFIG_* variables after building ? The closest I've got so far is using "bitbake -e linux-raspberrypi".15:30
LetoThe2ndmeego: look at the kernel build directory, the resulting .confg file should be there.15:31
meego@LetoThe2nd thanks15:31
frayif the kernel has embedded .config enabled, a copy will be in your running device.15:32
frayIf not, you'll have to dig it out of the build directory15:32
LetoThe2ndyeah once you got a system up and running thats the alternative.15:33
meegofray: yeah i tried that but it seems proc/config is disabled. Thanks15:33
JaMamaybe you need to modprobe configs first15:34
JaMaor even install the kernel-modules-configs first15:35
*** goliath <goliath!~goliath@> has quit IRC15:36
*** jobroe <jobroe!~manjaro-u@> has quit IRC15:40
*** fmo <fmo!c19ede6a@> has quit IRC15:45
*** frsc <frsc!~frsc@2003:a:e7a:6200:849b:24ee:ca9d:3215> has quit IRC15:45
meegoi see lots of kernel-related .config files in tmp/work & tmp/work-shared but they all seem to either be machine-specific or arch-specific. Where should the merged version be ?15:51
qschulzmeego: well... the kernel is machine specific? what's exactly your issue?15:56
*** diego_r <diego_r!> has quit IRC15:57
meegoqschulz: ah ofc. This looks like the one, isn't it ? (I'm building for RPi3) tmp/work/raspberrypi3-poky-linux-gnueabi/linux-raspberrypi/1_4.19.71+gitAUTOINC+13ce09db83-r0/linux-raspberrypi3-standard-build/.config16:01
qschulzmeego: what is your isse? why do you want to know about .config?16:02
meegoqschulz: i am missing some devices (empty /proc/asound/cards & /dev/rtcN) after switching my image's parent class from core-image to core-image-minimal. I want to make sure the kernel still has the necessary configuration to make both work. Plus now i also want to enable /proc/config.gz (modprobe didn't help)16:06
qschulzmeego: you can check whatever is enabled with a gui-like interface with bitbake -c menuconfig virtual/kernel but honestly it sounds weird. Maybe you're missing the kernel-modules, try to add that in your IMAGE_INSTALL or CORE_EXTRA_IMAGE_INSTALL16:08
qschulzmeego: and it seems weird because the image shouldn't be able to impact the packages at build time. only machine, distro or local.conf can16:09
qschulzso I guess you're just missing the kernel-modules. You can fine tune them and have only the ones you want to include either by modifying the defconfig of the kernel or include kernel-module-xyz instead of kernel-modules16:10
qschulzlet us know if that fixes it?16:10
meegoqschulz: that's useful pointers, thanks16:11
kroonRP, you know if using hashequiv and script plays along nice together ?16:11
JaMakroon: does the script work since the sstate-cache has another directory level?16:13
kroonJaMa, I haven't seen any error messages at least :-)16:14
kroon(yes i'm on master branches everywhere)16:14
kroonI'm a little confused concerning how hashequiv has changed things16:15
RPkroon: I don't...16:16
RPkroon: I'd have thought the common codepaths would still touch sstate access stamps so it should still work16:16
kroonRP, I was in a state where doing "bitbake openjre-8" always rebuilt, and bitbake-diffsigs didn't help. So I thought maybe confused things. So now I've wiped cache/ to remove the hashequiv db and rebuilding16:19
kroonAnd even though it rebuilt, I never saw any sstate cache being created16:20
RPkroon: I'd have thought it easier to debug when it was reproducing. I don't have any insight to offer offhand though :/16:20
* RP needs to focus on getting green autobuilder builds again16:20
LetoThe2ndRP: green? autobuilding for future?16:21
*** hpsy <hpsy!~hpsy@> has quit IRC16:22
*** hpsy <hpsy!~hpsy@> has joined #yocto16:22
RPLetoThe2nd: things are currently consistently failing :(16:25
*** RobertBerger <RobertBerger!> has quit IRC16:26
*** sathish22101992 <sathish22101992!31ce0b6b@> has joined #yocto16:27
*** goliath <goliath!> has joined #yocto16:29
*** sathish22101992 <sathish22101992!31ce0b6b@> has quit IRC16:32
kroonRP, no worries, just wanted to check if you had any thoughts on the matter16:33
*** Bunio_FH <Bunio_FH!> has quit IRC16:35
RPJPEW: Found a problem in kbd which I'm hoping may resolve some of the repro build issues16:38
*** fl0v0 <fl0v0!> has quit IRC16:40
*** ywang <ywang!~ywang@> has quit IRC16:46
*** ywang <ywang!~ywang@> has joined #yocto16:46
*** guerinoni <guerinoni!> has quit IRC16:56
*** kroon <kroon!~kroon@> has quit IRC16:57
*** Bunio_FH <Bunio_FH!> has joined #yocto16:57
RPJPEW: looking at a nice looking sledgehammer for the SHELL issue17:00
*** m1ster_r0b0t <m1ster_r0b0t!> has joined #yocto17:02
*** goliath <goliath!> has quit IRC17:05
armpitRP, the buildtools work for older and newer gcc's. Are we good for backporting yet?17:10
meegoqschulz: re-adding the kernel-modules did the job. Thanks again !17:14
RParmpit: you tested them?17:15
*** meego <meego!> has quit IRC17:16
*** leon-anavi <leon-anavi!~Leon@> has quit IRC17:19
armpitmaybe I am getting confused. are the binutils sdk changes needed?17:23
*** mmorton <mmorton!> has joined #yocto17:24
RParmpit: ultimately, yes. But we do really need to have some test branches and test them in the older releases first17:25
*** sagner <sagner!> has quit IRC17:25
RParmpit: we're missing the autobuilder pieces to do this right now17:25
rob_griesI am trying to build an image with development tools installed (gcc, gdb, g++, pkg-config..etc) but these tools are not being installed into my resultant image when supplying the following EXTRA_IMAGE_FEATURES += "tools-sdk tools-debug tools-profile tools-testapps package-management".17:27
rob_griesI am working with the APQ8053 and using the CAF supplied yocto-based bsp. Anyone have any ideas?17:28
armpitRP, ok.. Ill see what I can do17:28
RParmpit: if it helps I have the test branches I mentioned17:29
roussinmrob_gries: Maybe you can try to output environment of your build. bitbake -e your_image | less, and search for EXTRA_IMAGE_FEATURES to see if it's being set correctly?17:32
roussinmI would probably check IMAGE_FEATURES, instead.17:33
RPInteresting dilemma. Should we force CONFIG_SHELL to be /bin/sh or /bin/bash for configure? Forcing to /bin/sh isn't deterministic since it detects if its bash or not and changes its quoting mechanism :/17:36
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC17:41
*** mckoan is now known as mckoan|away17:41
*** rcw <rcw!~rcw@> has joined #yocto17:47
*** sk_tandt <sk_tandt!> has quit IRC17:50
*** pharaon2502 <pharaon2502!> has joined #yocto17:54
*** goliath <goliath!> has joined #yocto17:55
RPJPEW: build running with the above tweak, hoping it helps with the repro failures17:55
zeddiiRP: I've got a series for v5.4 that I can send out to the list, I was thinking of doing one more AB run, is there a better (or worse) time for that ?18:06
*** Bunio_FH <Bunio_FH!> has joined #yocto18:15
*** comptroller <comptroller!> has quit IRC18:15
*** Bunio_FH <Bunio_FH!> has quit IRC18:15
khemRP: bash is entrenched in autotools I have seen it elsewhere18:17
khemperhaps better to use bash always maybe :(18:17
*** Bunio_FH <Bunio_FH!> has joined #yocto18:18
khemrob_gries: usually this means someone is overwriting EXTRA_IMAGE_FEATURES you need to trace that perhaps bitbake -e is a good option to debug that18:18
rob_griesthanks, I'm looking that over now18:19
rburtonRP: force to bash18:19
khemusually best is to use _append EXTRA_IMAGE_FEATURES_append = " ...."18:19
*** Bunio_FH <Bunio_FH!> has quit IRC18:21
*** Bunio_FH <Bunio_FH!> has joined #yocto18:21
*** comptroller <comptroller!> has joined #yocto18:22
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC18:22
*** pharaon2502 <pharaon2502!> has quit IRC18:23
*** Bunio_FH <Bunio_FH!> has quit IRC18:26
tlwoernerJPEW: i assume you're using the uSD card on the rock pi 4?18:30
*** nerdboy <nerdboy!~sarnold@> has joined #yocto18:34
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto18:34
*** Bunio_FH <Bunio_FH!> has joined #yocto18:36
*** thannoy <thannoy!> has joined #yocto18:39
*** comptroller <comptroller!> has quit IRC18:42
smurrayarmpit: looking at meta-security's master-next, I see you fixed linux-yocto-dev.bbappend, but linux-%_5.%.bbappend is still present. That's effectively linux-%.bbappend, breaks e.g. linux-raspberrypi compile in AGL which has smack enabled...18:42
*** dreese <dreese!> has joined #yocto18:53
*** comptroller <comptroller!> has joined #yocto18:57
JPEWtlwoerner: Yes. I think the eMMC could be easily supported with another wks file19:02
*** Bunio_FH <Bunio_FH!> has quit IRC19:04
JPEWRP: Ya, I don't know which is better between /bin/sh and /bin/bash19:04
JPEWRP: I logged some of the repro problems in bugzilla... there are more though19:04
tlwoernerJPEW: how are you powering the board? when i plug it in i get nothing, no LEDs, nothing19:04
JPEWUSB-C charger from my phone?19:05
JPEWDo you have a serial console attached to the header?19:05
tlwoernerJPEW: serial? yes19:05
JPEWtlwoerner: The cheap one that used prevented it from booting in that way19:06
tlwoernermy ASUS chromebook USB-C adapter doesn't specify that it's "USB PD" or "qualcomm qc" so maybe that's my issue19:06
*** sno <sno!~sno@> has quit IRC19:06
JPEWtlwoerner: Maybe. Mine is from my Pixel 2... I haven't tried a more generic one.19:07
tlwoernerahh... unplugging the console cable the green LED now lights up19:07
*** Bunio_FH <Bunio_FH!> has joined #yocto19:08
JPEWtlwoerner: You can plug it back in after the light comes on19:08
JPEWtlwoerner: I got one of these and it works better:
JPEWtlwoerner: But beware: The green and white pins are backward19:10
tlwoernerthat's a new one, i've never seen a serial cable interfere with booting19:10
tlwoernersweet, it works (by plugging in the cable after booting)19:11
JPEWtlwoerner: I've had to put 100 Ohm resistors on almost all of mine because they were backpowering the boards19:11
JPEWtlwoerner: The only one that didn't have that problem was my raspberry Pi19:11
JPEWtlwoerner: Well, and the RockPi4... I suspect it was somehow holding the CPU reset pin19:12
*** Bunio_FH <Bunio_FH!> has quit IRC19:13
*** bornjre <bornjre!~manjaro-b@> has quit IRC19:19
*** sstabellini <sstabellini!sstabellin@gateway/shell/xshellz/x-stonyibohvsixlgf> has joined #yocto19:20
tlwoernerJPEW: when you say that one "works better" you mean it actually works? i.e. with no tricks?19:21
JPEWtlwoerner: Right, you can leave it plugged in all the time. It also can reach the 1.5 Mbaud speed that the RockPi4 uses (which my others couldn't)19:23
JPEWtlwoerner: I may have chosen poorly on my first batch, give how much trouble they've been :)19:23
tlwoernerokay, i'll grab one of those. i can't seem to find my adafruit console cable to see if that one will work19:23
tgamblintlwoerner: still no word from that prof?19:24
tlwoernertgamblin: sadly no. i'll poke him again, thanks for the reminder19:24
tgamblinNo worries19:25
tlwoernerJPEW: i've got a bunch of those "raspberry pi" ones from digikey/mouser, the speed seems fine, but they can't be plugged in at boot19:26
*** comptroller <comptroller!> has quit IRC19:26
*** dreyna <dreyna!> has joined #yocto19:26
tlwoernerJPEW: do you have a pic of the 100 Ohm tweak? are they just in series with the TX/RX lines?19:27
JPEWJust the TX line19:27
JPEWerr, USB TX -> Pi RX19:27
tlwoernerso the pin furthest from the ground?19:28
JPEWYes, I think so. Don't have the boards ATM19:28
JPEWtlwoerner: The idle signal level for serial is high, so the target device can end up accidenly drawing power from it.19:29
JPEWThe resistor makes it not able to draw enough to actually power anything :)19:29
tlwoerneri've noticed on other boards that often the serial cable will cause the onboard LEDs to glow ever so faintly, but i've never seen a case where the console cable prevented the board from booting :-)19:29
JPEWtlwoerner: Ya, I was paranoid so I added the resistors if the LEDs were lighting19:30
JPEWI've seen the serial prevent the CPU from resetting properly on power down... latches something high and the CPU doesn't reset properly19:30
*** comptroller <comptroller!> has joined #yocto19:34
*** muep <muep!> has joined #yocto19:41
*** dl9pf_home <dl9pf_home!~quassel@opensuse/member/dl9pf> has joined #yocto19:47
tlwoernerJPEW: in any case, it's pretty sweet to see the built images booting :-D19:50
tlwoerner...and it's nice to see the bmap stuff working19:51
ecdheI've got a kernel patch included through a recipes-kernel/*.bbappend.  I also have a user.cfg that I use to implement CONFIG_ options when building the kernel.  However, I don't appear to be able to set a CONFIG options that is defined by my patch.19:54
*** thannoy <thannoy!> has quit IRC19:55
tlwoernerJPEW: out of curiosity, what is the deploy class doing?19:59
ecdhethat is, my patch defines a whole new driver, and patches the makefile and kconfig files with CONFIG-dependent behavior.  But of course, when I run bitbake -c menuconfig virtual/kernel, I can't find my driver in the menu system because the patch hasn't been applied.19:59
JPEWtlwoerner: sets up do_deploy to do sstate properly:
tlwoernerJPEW: interesting! i thought all recipes had a deploy task by default. so a do_deploy is needed when manually stuffing things into the deploy folder? e.g. pre-compiled binaries?20:11
*** dev1990 <dev1990!> has joined #yocto20:13
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto20:16
*** sno <sno!> has joined #yocto20:17
*** agust <agust!> has quit IRC20:25
*** agust <agust!> has joined #yocto20:26
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:e587:cf72:a3a0:7abd> has joined #yocto20:34
khemRP: it seem bash change related ?20:38
*** atyagi2 <atyagi2!~ankurtyag@2407:7000:9031:dd00:c048:7736:ddd:d481> has quit IRC20:41
*** atyagi2 <atyagi2!~ankurtyag@> has joined #yocto20:42
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:e587:cf72:a3a0:7abd> has quit IRC20:44
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC20:49
*** atyagi2 <atyagi2!~ankurtyag@> has quit IRC20:53
RPkhem: possibly, yes21:13
*** berton_ <berton_!~berton@> has quit IRC21:14
RPkhem: almost certainly. I ran it through the autobuilder to see how bad the issue was21:14
RPkhem: the puzzle is how this issue didn't appear before now21:14
RPlooks like a problem with grep and xz21:14
khemRP: if I build it natively on my box then I dont see /bin/bash creeping in21:17
khemon xz21:17
RPkhem: your /bin/sh is ???21:18
*** dreyna <dreyna!> has quit IRC21:19
diamondman.join #grub21:20
khemRP: /bin/sh -> bash21:22
RPkhem: Its due to the way xz uses CONFIG_SHELL (before automake sets it to its other uses) :/21:23
RPkhem: we can fix that one...21:23
roussinmI'm trying to switch a recipe to a git repository instead of the tarball so that I can use devtool on the recipe (libnl), but when I try to build it now I get a message that whatever I try can't get it to go through the configure phase. aclocal: error: couldn't open directory 'm4': No such file or directory...  I tried with autotool-broken, no luck....21:30
RPJPEW: bigger question - why are we suddenly seeing so many repro build issues?21:34
khemRP: are you thinking of forcing gl_cv_posix_shell ?21:34
RPkhem: yes, testing that21:37
RPkhem: grep is a bit more of a pain, just sedding that one21:37
khemRP: that will be needed for all packages which use posix-shell.m4 macros I guess these are standard macros coming from m421:38
khemcome from gnulib
*** sagner <sagner!~ags@2a02:169:3df5::edf> has joined #yocto21:44
*** tgamblin <tgamblin!~tgamblin@> has quit IRC21:44
khemRP: peerhap EXTRA_OECONF += "gl_cv_posix_shell=/bin/sh" will do it21:48
RPkhem: CACHED_CONFIGUREVARS += "gl_cv_posix_shell=/bin/sh21:48
RPkhem: tweaks in -next, retesting21:56
JPEWRP: I really don't know :(21:56
RPJPEW: I'm not surprised we have some issues, I just don't understand how they all appear now21:57
*** pohly <pohly!> has quit IRC21:58
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto22:01
JPEWtlwoerner: I think the deploy.bbclass is needed by just about anything that has a do_deploy (precompiled binaries or not)22:05
JPEWAt least, if you want sstate, which you almost always do22:05
khemRP: sounds good, but changes to xz means recompiling everything almost perhaps I should add it to  ASSUME_PROVIDED22:11
RPkhem: its hard as it means liblzma headers as well22:12
*** rcw <rcw!~rcw@> has quit IRC22:13
JPEWRP: Do we run the reproducible test on all AB hosts?22:14
*** RobertBerger <RobertBerger!~rber@> has joined #yocto22:18
RPJPEW: yes22:21
RPJPEW: well, most22:21
JPEWRP: my only guess is that the ones we do run it on are "close enough" to similar that it doesn't matter, but the sstate was populated from one of the ones we don't run it on and it's different enough to matter22:23
JPEWBy using sstate, we are effectivly saying that we want reproducible across different hosts. Not that we shouldn't do that, but it's more strict that most other reproduciblity initiatives.22:24
RPJPEW: I just don't understand what changed as sstate is suddenly always bad :/22:27
*** WillMiles <WillMiles!~Will@> has quit IRC22:40
*** dfaught <dfaught!~dfaught@> has joined #yocto22:46
*** sk_tandt <sk_tandt!> has joined #yocto22:48
*** dfaught <dfaught!~dfaught@> has quit IRC22:53
*** sk_tandt <sk_tandt!> has quit IRC22:53
ecdhei figured it out, the patch that implemented the CONFIG item hadn't been applied because it wasn't in my layer.22:53
tlwoernerJPEW: yes, i was just using that as one example, sorry for being confusing22:58
*** pbb_ <pbb_!> has joined #yocto22:58
tlwoernerit just struck me as odd because i hadn't thought about it in depth before: although there's a lot of "stuff" that happens, at the end of the day, very few things make their way to the deploy directory22:58
tlwoernerso, in a funny twist, deploying is a non-default case22:59
*** pbb_ <pbb_!> has quit IRC23:04
*** pbb <pbb!> has joined #yocto23:08
*** agust <agust!> has quit IRC23:18
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC23:20
*** rburton <rburton!rburton@nat/intel/x-hihjswglddlpbuwd> has quit IRC23:27
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC23:44

Generated by 2.17.2 by Marius Gedminas - find it at!