Thursday, 2020-02-20

armpitKhem, too much tea for you00:07
*** goliath <goliath!> has quit IRC00:20
*** tolszak_ <tolszak_!> has quit IRC00:20
*** tolszak_ <tolszak_!> has joined #yocto00:22
mcccHello, I have a set of recipes I want to each build multiple packages, one per 'username,' and I want to define the usernames in a common list ${MY_USERNAME_LIST} included in each recipe.00:38
mcccI can split and loop ${MY_USERNAME_LIST} in to ${MY_USERNAME} inside do_install(), but is there a good way I can dynamically create the appropriate FILES_${MY_USERNAME} = "/home/${MY_USERNAME}" and pkg_postinst_${MY_USERNAME}_append() and pkg_prerm_${MY_USERNAME}_append()  functions?  Is this an appropriate idea?00:38
zeddiikhem: ack’d. I’m finishing some testing and can add it shortly.00:40
*** sdude <sdude!cb1f2c1e@> has joined #yocto00:46
*** gtristan <gtristan!~tristanva@> has joined #yocto00:47
*** vineela <vineela!~vtummala@> has quit IRC00:57
*** sdude <sdude!cb1f2c1e@> has quit IRC01:03
*** sdude <sdude!cb1f2c1e@> has joined #yocto01:22
xyzzy42I'm trying to replace a "defconfig" file the meta-ti layer with one in my own meta layer.  I've prepended "${THISDIR}/${PN}:" to FILESEXTRAPATHS, yet it's not working.01:38
xyzzy42I've checked that FILESEXTRAPATHS for the kernel does have my meta layer first, the path is correct, there is a file named "defconfig" in the named directory, etc.01:38
xyzzy42is there a debug tool to see in more detail how "file://defconfig" is resolved and why the first matching file in FILESEXTRAPATHS is not the one used?01:40
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC01:42
denixxyzzy42: most probably because machine-overrides take precedence. put your defconfig in the ${PN}/<machinename>/ directory in your layer and see if that helps. don't change FILESEXTRAPATHS01:43
*** gasa1 <gasa1!~gasa@> has joined #yocto01:44
*** gasa <gasa!~gasa@> has quit IRC01:45
xyzzy42denix, The machine-overrides directory is probably one of the directories listed in FILESPATH?  I do see that there is a dir under meta-ti that exists in FILESPATHS.01:47
xyzzy42denix: Thanks, that got me on the right tack.  I did need to modify FILESEXTRAPATHS too and also place the file in a machine override directory in my layer01:56
*** lexano_ is now known as lexano01:57
xyzzy42The problem appears to be FILESEXTRAPATHS of dir1:dir2 with machine mach1 results in a final search order of dir1/mach1:dir2/mach1:dir1:dir201:57
xyzzy42So a file in dir2/mach1 takes precedence over dir1, even though dir1 is before dir2 in the path search order.01:58
sdudeHi all, I'm banging my head against a wall trying to have a header file appear in my generated SDK02:00
sdudeinserting the missing header to the SDK)02:00
khemzeddii: thanks, this should go along with
denixxyzzy42: your FILESEXTRAPATHS should not have machine directories listed - those are standard OVERRIDES and those are expanded automatically02:10
xyzzy42denix: It does not.  But FILESPATH does have them, and it appears that's what the final search order is.02:11
denixxyzzy42: the issue is that if underlying layer already has machine-override files (e.g. dir1/mach), then your additional layer won't be able to just use files in dir1 or dir2 - the easiest way is to place your new file under dir2/mach and point FILESEXTRAPATHS to dir202:14
denixxyzzy42: correct, you don't list <mach> dirs in FILESEXTRAPATHS - all the OVERRIDES will be automatically expanded into the final FILESPATH list02:16
*** vdehors_ <vdehors_!> has quit IRC02:30
*** dev1990 <dev1990!> has quit IRC02:34
*** vdehors <vdehors!> has joined #yocto02:35
*** stephano <stephano!> has quit IRC02:37
*** ka6sox is now known as zz_ka6sox03:16
*** ericch <ericch!> has quit IRC03:34
*** hyper_dave <hyper_dave!~quassel@> has quit IRC03:44
*** hyper_dave <hyper_dave!~quassel@> has joined #yocto03:45
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC04:42
*** champagneg <champagneg!> has quit IRC05:27
*** roussinm <roussinm!> has quit IRC05:28
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC05:49
*** champagneg <champagneg!> has joined #yocto05:52
*** roussinm <roussinm!> has joined #yocto05:52
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto06:22
*** zz_ka6sox is now known as ka6sox06:25
*** pohly <pohly!> has joined #yocto06:47
ningaubleHi all, is there a Xenomai Mercury and/or Cobalt layer for raspberrypi3-64 for kernel 4.19 or better?  I'm trying to cobble my own together but would love to know if there's already one out there.06:57
ningaubleSo far I've found this: which I'm using as a starting point07:00
*** guerinoni <guerinoni!> has joined #yocto07:04
*** comptroller <comptroller!> has quit IRC07:05
*** kaspter <kaspter!~Instantbi@> has quit IRC07:08
*** kaspter <kaspter!~Instantbi@> has joined #yocto07:08
*** agust <agust!> has joined #yocto07:13
*** guerinoni <guerinoni!> has quit IRC07:16
*** palate <palate!> has quit IRC07:16
*** palate <palate!~palate@unaffiliated/palate> has joined #yocto07:16
*** mattsm <mattsm!> has quit IRC07:16
*** guerinoni <guerinoni!> has joined #yocto07:17
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto07:18
*** mattsm <mattsm!> has joined #yocto07:18
*** comptroller <comptroller!> has joined #yocto07:22
*** TobSnyder <TobSnyder!~schneider@> has joined #yocto07:24
*** jobroe <jobroe!~manjaro-u@> has joined #yocto07:24
erboningauble: If I look at I find:
*** jobroe <jobroe!~manjaro-u@> has quit IRC07:26
*** jobroe <jobroe!~manjaro-u@> has joined #yocto07:27
LetoThe2ndningauble: this is the very best place to get started with xenomai:
*** frosteyes <frosteyes!~frosteyes@> has quit IRC07:32
ningaubleerbo:  many thanks; that tree appears to be stuck back at 4.9 while I'm looking for 4.19+...  Maybe I can adapt it as well.07:32
ningaubleLetoThe2nd:  thanks also, I'll see if I can find what I need in there too07:34
LetoThe2ndgood luck. i failed with that... no free beer in there.07:34
*** fitzsim <fitzsim!> has quit IRC07:35
ningaublePREEMPT_RT is easy enough, but for some reason Xenomai via Yocto eludes me07:35
LetoThe2ndningauble: in the repo given are recipes etc. for xenomai on 4.19. you only have to add in a raspi kernel config, then you should be good to go.07:36
*** frsc <frsc!> has joined #yocto07:37
ningaubleHmm...  I see only 4.9.45 but I'll dig deeper in the morning.  Again thanks for the assist!07:39
ningaubleOh, right on..!  Thanks07:40
ningaubleI had confused that repo with erbo's link to OE; sure enough that'll do07:42
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto07:43
*** frosteyes <frosteyes!~frosteyes@> has joined #yocto07:44
*** m1ster_r0b0t <m1ster_r0b0t!> has quit IRC07:44
*** kreyren[m] <kreyren[m]!~kreyrenm]> has quit IRC07:44
*** kreyren[m] <kreyren[m]!~kreyrenm]> has joined #yocto07:44
*** dreyna <dreyna!> has quit IRC07:45
*** fl0v0 <fl0v0!~fvo@> has joined #yocto07:50
*** yacar_ <yacar_!> has joined #yocto07:57
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC08:18
*** hyper_dave <hyper_dave!~quassel@> has quit IRC08:24
*** rubdos_ <rubdos_!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto08:28
*** hyper_dave <hyper_dave!~quassel@> has joined #yocto08:29
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC08:30
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:31
stuom1anybody familiar with cve-check? How can I get a log that only shows unpatched ones?08:32
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto08:46
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto08:46
*** yacar_ <yacar_!> has quit IRC08:50
*** Bunio_FH <Bunio_FH!> has joined #yocto08:53
stuom1also about cve-check, bitbake give many error that it cannot compare version when there is a "+"-sign in version string (and there is many such packages), but still in final log those are marked as "patched"?08:55
*** florian_kc is now known as florian08:56
*** gasa2 <gasa2!~gasa@> has joined #yocto09:00
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto09:00
*** gasa2 is now known as gabrielssanches09:00
*** yacar_ <yacar_!> has joined #yocto09:01
*** gabrielssanches <gabrielssanches!~gasa@> has quit IRC09:01
*** gasa1 <gasa1!~gasa@> has quit IRC09:04
*** goliath <goliath!> has joined #yocto09:05
*** hpsy <hpsy!~hpsy@> has joined #yocto09:23
*** nerdboy <nerdboy!~sarnold@> has joined #yocto09:23
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto09:23
*** tomeccles <tomeccles!~tomeccles@> has joined #yocto09:24
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:33
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto09:46
mcfriskstuom1: master, zeus or some other branch? cve-check does throw warnings of all unpatched CVE to bitbake output. Then both patched and unpatched are listed in tmp/deploy/cve/ for recipes and images. image output includes all development tools which makes it for me a bit useless. sadly whitelisted CVEs are not listed in the reports. Have not seen the + issue myself, but feels like a bug.09:46
*** opennandra <opennandra!> has joined #yocto09:49
*** dreyna <dreyna!> has joined #yocto09:51
*** gaston53 <gaston53!c50146d0@> has joined #yocto09:51
gaston53Hello, afteradding Boost library into my SDK in Yocto project, I want to know if there is a hint or something that let me know which compiler is used to build this library into my project09:53
LetoThe2ndgaston53: can you rephrase?09:53
gaston53I am using Yocto project. I bitbake the SDK toolchain. I added the " boost " library into this toolchain. I don't know which compiler is used in order to build this library into the toolchain09:55
LetoThe2ndgaston53: i got the first two parts. but the last part doesn't make sense to me.09:55
LetoThe2ndgaston53: are you asking which compiler built the boost libraries?09:56
gaston53I thought that the boost libraries name will be like this : " boost_lib_atomic_gcc_mt " or something like this, here I can find that the compiler is " gcc "09:56
*** opennandra <opennandra!> has quit IRC09:57
gaston53libboost_atomic is only what I find in the name of the lib09:57
LetoThe2ndgaston53: what is it that you *ACTUALLY* want to do?09:57
LetoThe2ndbecause this sounds massively like an XY question. you want to do X, and are stuck. you think that Y is a way to solve it. you are stuck on Y again, and thats what you ask us. please ask about X directly.09:58
*** NiksDev <NiksDev!~NiksDev@> has quit IRC09:59
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto09:59
gaston53In a CMake project Debug, it tells me that " boost_COMPILER = "-gcc74" (guessed)09:59
*** JoeR <JoeR!> has joined #yocto09:59
gaston53I want to add a variable in this project and specify the real compiler10:00
gaston53I am confused about this " guessed "10:00
JoeRHi all, hopefully a quick question. I needed to tweak sysctl.conf. I use procps within my image, and added a bbappend to procps to refer to my sysctl.conf10:01
LetoThe2ndnailing down the compiler in the project is bad10:01
JoeRHowever it seems another package must override the procps sysctl.conf file as the one within procps does not seem to eventually end up in my image.10:01
JoeRAm I fighting multiple recipes supplying sysctl.conf somehow?10:01
LetoThe2ndgaston53: why do you even care about the specific compiler? i mean, cmake can find and use boost without firther ado.10:01
qschulzgaston53: I think we're in the XYZ situation, where you've now given us Y and Z, please give us X :D What exactly are you trying to achieve, like the actual problem. Why do you care to know the compiler?10:02
LetoThe2ndqschulz: ++10:02
qschulzLetoThe2nd: you beat me to it that time :)10:02
*** opennandra <opennandra!> has joined #yocto10:02
LetoThe2ndqschulz: better this than proposing to you, don't you agree?10:03
gaston53LetoThe2nd qschulz Beacause I have multiple boost libraries with the same version on my machine which are build differently10:03
stuom1mcfrisk: im using thud10:03
gaston53I will delete them than10:04
LetoThe2ndgaston53: but hopefully only ONE in the sdk.10:04
qschulzLetoThe2nd: depends, if you're offering unlimited lifetime beer supply, we might find some common ground ;)10:04
LetoThe2ndgaston53: and if your crossbuild refers to something on the dev host, you're deeper in trouble than you even realize10:04
LetoThe2ndqschulz: i though you would bring the beer supply?10:05
gaston53LetoThe2nd I am hating my life on this project anyway10:05
qschulzLetoThe2nd: I drink mostly IPAs, so you'll be sad if I do. Let's call this thing off.10:05
mcfriskstuom1: you might want to backport a lot of cve-check related changes from master branch. I did this also for sumo..10:06
LetoThe2ndgaston53: to be honest, my impression is that because you are clinging to wrong pre-assumptions coming from non-cross development.10:06
LetoThe2ndqschulz: hm. yeah. "sorry darling, it couldn't ever have worked!"10:06
qschulzLetoThe2nd: let's stay friends, better for both of us.10:07
LetoThe2ndqschulz: *nods and sobs*10:07
gaston53LetoThe2nd you are right .. I guess ..10:07
stuom1mcfrisk: ok, I will try10:07
LetoThe2ndgaston53: and to be even more honest, i think all that dance arond the SDK is causing a lot of the troubles.10:08
qschulzLetoThe2nd: there there10:08
LetoThe2ndgaston53: why don't you "just" take your build, devtool add whatever you proejct is and see what happends?10:08
LetoThe2ndgaston53: i even walked through the process in a, however introductory fashion just yesterday...
JoeRHmm. OK. Sorted my own problem. Had sysctl.conf in a ${PN} subdir and not a files subdir. Seems like it didn't get packaged from there? Didn't think the main recipe cared though...10:14
gaston53LetoThe2nd cross compiling with SDK is not my problem, I have succeded to cross compile a c++ program using the SDK toolchain and executed it on remote platform, I have created a makefile and mentioned what I need from the SDK ( compiler ) and Boost library ( which is the most complicated library I have ever seen ) and all run well10:14
*** FrazerClews <FrazerClews!> has joined #yocto10:15
LetoThe2ndJoeR: the search path for things the recipe refers to is basically either a "files" subdirectrory or "${PN}" subdirectory.10:15
LetoThe2ndJoeR: bitbake -e your thing and look for FILEEXTRA-something to find out more.10:15
gaston53LetoThe2nd But I am facing a lot of problem trying to use all these in VisualStudio with the details of CMake project10:15
LetoThe2ndgaston53: see, *NOW* we have finally reached X.10:16
gaston53LetoThe2nd my objective is to set a suitable configuration CMake project which will make a program run on multiple platforms architecture10:16
JoeRYeah, that's what I thought. I didn't think it cared, I did the FILESEXTRAPATHS_prepend of ${THISDIR}/${PN}10:16
gaston53using SDK , boost , and other tools10:17
LetoThe2ndgaston53: because the *REAL* question is, "how do i make the sdk and cmake play nice with VS"10:17
JoeRAnd had the file in a procps subdir of procps. bitbake was happy to build that. But I never got my file in the rpm.10:17
gaston53LetoThe2nd That's it10:17
JoeRChanging to a files subdir and it all just worked.10:17
LetoThe2ndgaston53: please mention this very early the next time, because most people here do not care about VS. i do not, too.10:18
qschulzJoeR: FILESPATH to be checked with bitbake -e, then you'll understand much more (or have a look at WORKDIR/temp/log.do_fetch (I think? or unpack)) There you have the order. I've been bitten by this one thing before as well :)10:18
LetoThe2ndgaston53: as long as the build process in itself works, we are happy. don't get me wrong - i understand the use case. but it is soemthing i do not want to support and spend time on.10:18
gaston53LetoThe2nd Why you do not care about VS ?10:18
LetoThe2ndgaston53: pay me, and then i will care.10:19
JoeRqschulz: Thanks, much appreciated :-)10:19
*** JoeR <JoeR!> has quit IRC10:19
gaston53LetoThe2nd haha they are paying me, I am forced to care ;)10:19
*** JoeR <JoeR!> has joined #yocto10:20
erbogaston53: Have you seen ?10:20
LetoThe2ndgaston53: then please care. seriously, whenever VS is involved, its a dead sure sign that some business forces are behind it. and i do not offer free services. thats why i specifically don't care about VS. other opinions are of course valid, i am speaking only for myself.10:20
qschulzgaston53: most likely some paths you haven't set so that VS can find your libboost in your SDK. VS should find the libboost from the SDK, not your build machine? But honestly, I'm a cli guy, so that's way out of my knowledge base now. GL10:21
LetoThe2nderbo: nice one.10:21
erboI haven't seen it myself, but it seems quite relevant here :)10:21
*** JoeR <JoeR!> has quit IRC10:21
LetoThe2nderbo: i'll skim it for referral10:22
LetoThe2ndand the above statement really was not a personal rant or such. please do not take it as such, anybody. its just my POV.10:22
gaston53qschulz LetoThe2nd It's okey! by the way, I have succeded also to cross compile a program with VS whichi is on my windows machine and run it on Linux using Boost. I am going step by step .. you see ..10:24
gaston53the path of boost lib is not a problem10:25
gaston53Now I am facing a problem with SDK10:26
gaston53He can not set the compiler that I need into its configurations10:26
gaston53it's usualy using the default compilers generated bu VS10:27
gaston53LetoThe2nd Another thing, it's an early morning here in my country :D10:27
LetoThe2ndgaston53: its always early morning somewhere.10:28
gaston53LetoThe2nd qschulz I just want to ask, what I am trying to do is difficult or just me I am finding it difficult ?10:36
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:39
LetoThe2ndgaston53: it is not exaclty difficult in the technical sense, probably. but its something that is usually solved by hours and hours wasted in tinkering settings back and forth. only for the sake of some company insisting on using windows.10:39
gaston53LetoThe2nd I totaly agree with you ! ( but its something that is usually solved by hours and hours wasted in tinkering settings back and forth )10:41
LetoThe2ndgaston53: and as it is a) time-intensive b) almost certainly not giving back any profit to the project or community - on the other hand, rather eating up support resources we have - i am highly reluctant to partake in such.10:42
LetoThe2ndgaston53: i mean, i'm pretty certain that there are solutions for that from vendors who base their products off yocto/OE technology.10:43
gaston53LetoThe2nd I see you are right10:44
*** rburton <rburton!~rburton@> has joined #yocto10:48
* LetoThe2nd is impressed. new session on youtube, 100 view in the first 12 hours.10:48
*** Bagira <Bagira!Phanes@2600:3c02::f03c:91ff:fe92:354e> has joined #yocto10:51
*** Bagira <Bagira!Phanes@surro/founder/phanes> has joined #yocto10:51
qschulzLetoThe2nd: soon a rockstar I see10:53
LetoThe2ndqschulz: \m/10:55
LetoThe2ndnow i'm hungry.10:56
*** camus1 <camus1!~Instantbi@> has joined #yocto10:59
*** kaspter <kaspter!~Instantbi@> has quit IRC10:59
*** camus1 is now known as kaspter10:59
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto11:02
*** FrazerClews <FrazerClews!> has quit IRC11:03
*** FrazerClews <FrazerClews!> has joined #yocto11:03
*** siva <siva!48a3dc10@> has joined #yocto11:04
*** ecclescake <ecclescake!~tomeccles@> has quit IRC11:04
*** rubdos_ <rubdos_!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC11:05
sivai am getting build error when i tried to build custom bsp layer with new machine type11:08
sivamy board is based on imx6ulevk11:08
siva| /nobackup/sikumar3/inode_sumo/buildnew/tmp/work/imx6uloib-poky-linux-gnueabi/linux-imx/4.14.98-r0/temp/run.do_compile.11826: line 181: arm-poky-linux-gnueabi-gcc: command not found11:08
sivathe error goes away if i rename the meta-mynode-board/recipes-kernel/linux/linux-imx_%.bbappend to  meta-mynode-board/recipes-kernel/linux/linux-fslc_%.bbappend11:10
sivabut the kernel build ignores my custom patches11:11
*** ecclescake <ecclescake!~tomeccles@> has joined #yocto11:11
LetoThe2ndsiva: there error goes away because it is not being built then.11:12
sivathe error appears when it tried to build the kernel files. as soon as i change the name, kernel is build successfully. but my custom changes are not applied (dts, drivers.patch etc)11:13
LetoThe2ndsiva: thats just what i said. if you rename th bbappend, it refers to a whole different recipe, which is not being built. hence the errors go away - as what you did is being ignored.11:14
LetoThe2ndsiva: i would say, remove stuff from your bbappend until things start working again.11:15
sivaok, do i need to remove my custom changes (defconfig, drivers.patch, dts etc) until it builds?11:16
*** gaston53 <gaston53!c50146d0@> has quit IRC11:22
*** guerinoni <guerinoni!> has quit IRC11:23
*** dreyna <dreyna!> has quit IRC11:25
sivawow! it builds now without my changes11:27
*** berton <berton!~berton@> has joined #yocto11:27
sivait got stuck with | make[3]: *** No rule to make target `arch/arm/boot/dts/imx6ul-mynode.dtb'.  Stop11:28
*** ecclescake <ecclescake!~tomeccles@> has quit IRC11:29
*** ecclescake <ecclescake!~tomeccles@> has joined #yocto11:32
*** yacar_ <yacar_!> has quit IRC11:37
*** Zajc <Zajc!> has quit IRC12:03
*** Zajc <Zajc!> has joined #yocto12:05
*** rburton <rburton!~rburton@> has quit IRC12:17
*** tgamblin <tgamblin!> has quit IRC12:28
*** rburton <rburton!rburton@nat/intel/x-tqsxnmzendaewftp> has joined #yocto12:30
*** tolszak_ <tolszak_!> has quit IRC12:34
*** siva <siva!48a3dc10@> has quit IRC12:36
*** frsc <frsc!> has quit IRC12:39
*** frsc <frsc!> has joined #yocto12:42
rburtonRP: whats the gst reproducible failure?12:43
RPrburton: that is fixed now, patch in master?12:48
rburtonah cool just read the summary :)12:48
RPrburton: not upstreamed yet12:48
RPrburton: found another perl issue, makefile race. Upstream merged that fix an hour ago :)12:49
qschulzI'm having a hard time understanding the use for multiple strings in BBFILE_COLLECTIONS in conf/layer.conf. What am I missing?12:52
LetoThe2ndqschulz: i'm just having a hrd time.12:54
RPqschulz: its very old code, it predates layers12:54
rburtonRP: enjoying how perl-cross maintainer is responsive12:56
qschulzLetoThe2nd: I'm sorry, I didn't think calling off would make you that sad.12:56
rburtonRP: i don't think you broke master in my absence ;)12:56
LetoThe2ndqschulz: hrhrhr12:56
RPrburton: yes, we need to get some other things submitted12:57
qschulzRP: ack, thanks12:57
LetoThe2ndqschulz: nah, i'm just dabbling in some horrible js with an angular 1 frontend.12:57
RPrburton: heh, have to try harder :)12:57
LetoThe2ndqschulz: and my "contributions" are basically just making it even uglier.12:57
LetoThe2ndqschulz: OTOH, if we handn't called off we could get divorced. we're missing out on that.13:00
qschulzLetoThe2nd: I've been dealing with vendor out-of-tree WiFi driver for the last month. Damn race between main thread and interrupt handler. Fixed it, tested it... OH an other one later. I feel you.13:01
qschulzLetoThe2nd: we're missing on two parties. Wedding and divorce. Such a shame13:01
LetoThe2ndqschulz: and worst of all, a proper irish funeral!13:02
LetoThe2ndoh wait.13:02
LetoThe2ndthat not realted, right?13:02
*** sdude <sdude!cb1f2c1e@> has quit IRC13:02
qschulzAny reason for other than use with devtool?13:03
qschulzI'm hunting down warnings and this "NOTE" message which isn't one is triggering me :)13:03
RPqschulz: you can use it standalone and it predates devtool!13:03
RPqschulz: specifically, that note is there to remind people its in use as for some scenarios, people forget13:05
qschulzRP: what do you mean by "it"? externalsrc?13:05
RPqschulz: yes. I didn't notice the n172 at first13:05
qschulzRP: I'm puzzled... If I decided I want externalsrc in my recipe, I have it? Why would I want a note?13:06
qschulzbut since externalsrc is used with devtool, I definitely want to know when the devtool bbappend is applied which inherits externalsrc. SO that one use for the note which isn't one, I understand :)13:07
RPqschulz: its probably more devtools focused13:07
qschulzCould this be moved to devtool then?13:08
qschulzWhen it creates the bbappend in devtool's workspace? (just asking, I'm not asking for someone to write the patch ;) )13:08
qschulzLetoThe2nd: you made me check what Irish Funeral is and the Urban Dictionary is definitely giving me weird vibes. Are you threatening me?13:09
RPqschulz: I'd guess. I'm not an expert on that code :(13:09
qschulzRP: alright, thanks. At least not opposed to the idea of that patch :)13:10
RPqschulz: We just don't have someone responsively maintaining that area of the code13:11
RPI'm worried about it :(13:11
zeddiiLooks like I fixed the last two non-reproducible build errors in my last 5.4 run13:12
qschulzRP: It just works (TM)13:12
zeddiiI’ll submit a series later today once I collect one more fix that khem pointed to yesterday.13:12
RPqschulz: until people patch it and change it13:13
qschulzRP: (don't look up who are the latest contributors to determine the maintainer though ;))13:13
RPzeddii: cool, thanks13:13
*** guerinoni <guerinoni!> has joined #yocto13:13
RPzeddii: perf fails on master with new binutils, looks like command whitespace issues :(13:13
qschulzRP: though it does not work (or does not work in an optimal way) if externalsrc is part of a git worktree but I haven't decided how to fix that properly yet (and we don't need it at work so... low prio).13:14
RPqschulz: first step would be to write a testcase!13:15
*** muppe <muppe!> has joined #yocto13:16
*** tgamblin <tgamblin!~tgamblin@> has joined #yocto13:20
zeddiiRP: that’s the patch that I have from khem. It’ll be in my series today.13:24
RPzeddii: ah, cool13:27
RPzeddii: also a bit worried about the whitespace command issue jwessel mentioned btw. Did we ever dig into that?13:27
zeddiino. I’ll have to dig up the original post. Was that where the flags order was implicated (even if not true)?13:28
RPzeddii: it was where a bit of trailing whitespace on the LD command (or some other toolchain variable) was breaking things13:29
zeddiiI’ll troll my saved email and have a look.13:30
RPzeddii: it looked bad/odd but I haven't had time to poke :(13:30
RPzeddii: yes, we can hack fix it but it suggested deeper issues13:30
* RP starts to ponder the ptest log with 2.1 million lines performance "problem"13:31
*** JoeR <JoeR!> has joined #yocto13:38
JoeRHi all. I'm back asking inane questions...13:39
JoeRSo. I need the licences within my image. I can get this by setting a few vars in local.conf13:39
JoeRHowever I have two images (one large, one an initrd) within my yocto project, both for the same board.13:39
JoeRI don't believe those vars are applicable in an an image recipe, however I don't want the licences within the initrd.13:40
JoeRIs there a way to do this that's cleaner than appending the vars to local.conf in between image builds?13:40
LetoThe2ndJoeR: sounds like a use case for multiconfig, with the licensing add ons only in the main images configuration13:41
JoeROK. I've not heard of multiconfig. I'm still stuck in Korgoth world (parallel dev to move forward to Thud). Is it available there?13:41
LetoThe2ndJoeR: technically it needs some tweaking, as you would have to include licensing texts that are only referring to software in the initrd then in the main image.13:41
LetoThe2ndJoeR: in thud, yes. krogoth, no.13:42
JoeRThe initrd is a perfect subset of the main image at least. I do nothing clever.13:42
JoeROK. So I'm stuck with my approach until I get to thud.13:42
JoeRThat's ok. As long as I know.13:42
JoeRYou're always so helpful. I say thanks again Leto!13:43
LetoThe2ndthrow free beer!13:43
JoeRIt's a long way from the UK to throw a beer!13:43
LetoThe2ndyou'll never succeed if you don't try!!!13:44
JoeRMeh, I'm on the continent in a few weeks anyway. It'll be easier from there.13:45
* LetoThe2nd senses a lame excuse here.13:45
*** banoli <banoli!~cpastore@> has quit IRC13:52
*** banoli <banoli!~cpastore@> has joined #yocto13:52
RPJoeR: which variables are these?13:55
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC13:56
RPJoeR: COPY_LIC_* are image specific so you could override on a per recipe basis14:03
RPJoeR: The latter package creation is global14:04
JoeROK. I might be able to do things in a better way then. Not sure I need package creation.14:04
RPJoeR: You could try LICENSE_CREATE_PACKAGE globally and something like  COPY_LIC_MANIFEST_pn-<my-image-recipe-name> ?14:04
JoeRIs there any clever/quick way I can determine what you just told me? i.e. how can I find out where certain variables are applicable? Other than RTFMM?14:05
RPJoeR: well, I did a grep for COPY_LIC and then looked at where its used14:06
RPJoeR: the code looks image specific to me14:07
JoeRRighto. Just wanted to be sure I wasn't missing a trick. You've let me know of things in the past that magically make my life way easier.14:07
RPJoeR: it would be good to document variable context but we don't have that :(14:07
qschulzRP: i second that. That would be extremely nice :)14:08
*** maudat <maudat!~moda@> has joined #yocto14:08
RPqschulz: question is someone to do it14:08
JoeRIt's a big project and it helps a lot of people. I'm just grateful it exists. I used ot have build distros entirely from scratch, this is a whole world better.14:08
RPJoeR: we are in some ways struggling to exist as nobody wants to help support the core :(14:09
RPJoeR: perhaps you could send a patch adding something to the manual about that class and those variables being image specific?14:09
LetoThe2ndRP: "the age of the everage RP increate by 1 each year"14:10
JoeRI'll see what I can do. Where's the manual live?14:11
RPJoeR: yocto-docs repo14:11
JoeROK. I'm under pressure at work, but I'll see what I can do.14:11
RPJoeR: well, hopefully we did just save you some time14:13
JoeRIndeed. I see that. People not so au fait with the open source world don't see things quite the same way.14:14
*** stephano <stephano!> has joined #yocto14:14
*** leon__ <leon__!~leon@> has quit IRC14:15
RPJoeR: I'm struggling to reply to that.14:17
RPJoeR: I do understand it, however the project could cease to exist if we don't find new contributors, even just for "small" things like docs tweaks14:18
LetoThe2ndand free beer!14:19
RPI say "small" since the whole project is build by many small incremental improvements building something greater.14:19
* LetoThe2nd gladly not only accept small free beers, also large ones!14:19
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC14:20
tgamblinLetoThe2nd: I foresee a joint Yocto & craft beer convention in the future14:20
LetoThe2ndtgamblin: i'm not exactly fond of craft beer in many cases, but count me in.14:20
JoeRIs craft beer even allowed under the reinheitsgebot?14:21
*** JaMa <JaMa!~martin@> has joined #yocto14:21
*** Zajc <Zajc!> has quit IRC14:21
LetoThe2ndJoeR: it is, yet maybe not in the same form of "craft" as in other countries.14:22
JoeRLetoThe2nd: Interesting. I've got quite used to weird lagers lately. Everything seems to be sour or with cucumber of some weird stuff.14:24
tgamblinLetoThe2nd: JoeR: <-- exceptional14:25
LetoThe2ndtgamblin: hrhrhr.14:26
LetoThe2ndtgamblin: i'm just like more of augustiner edelstoff guy.14:26
JaMaanyone still using svn fetcher activelly? Did the path where the sources are checked out changed "recently" (before thud release)?14:26
RPI've taken some significant risks to keep the project alive, I'm starting to feel rather lonely on the "core" issues though and wondering why I keep doing it when its clearly making me ill. Looking at my buglist is totally depressing :(14:27
RPJaMa: there was a fix I just merged which may be relevant14:27
RPJaMa: not the last svn change but the one before14:27
JaMaRP: thanks, I'll check, I'm doing some world builds again and surprisingly all svn users in meta-oe are failing either to populate_lic or patch because of missing files (because S points to wrong dir)14:29
JaMaand I can reproduce it in thud as well as master (as of yesterday)14:29
JaMaand it's not listed in khem's report for some reason14:29
RPJaMa: hmm, we dropped all the svn urls from the core so its not that well tested now14:30
JaMaI already have "75223644 fetch2: svn: care for path_spec" if that's the one you had in mind14:31
JoeRRP: I was under the impression that the Yocto project had active support, active members funded by the larger corps? Intel etc.?14:31
JaMa[Sno]: around?14:32
RPJoeR: Intel has pulled back a lot of the people and is no longer doing development on the core. Other members have stepped up with funding and I'm now funded by that for example but what we're missing is people to do things :(14:33
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:33
JoeRRP: This is somewhat of a tragedy then :-(14:33
RPJoeR: I've put together contingency plan upon contingency plan but without developer time on issues there are limits on what can be done14:36
JoeRRP: That I can well believe. This is a small part of what I do as my job, that's only the case because Yocto exists though.14:37
*** dev1990 <dev1990!> has joined #yocto14:39
RPJoeR: the model was we're all supposed to share the maintenance of the core. That isn't really happening as well as it needs to14:40
JoeRRP: Do many people understand the core? I just use Yocto as a tool, so have no real understanding of how it's working most of the time.14:43
RPJoeR: There are people but many are pulled onto other things by their employers14:46
RPJoeR: I've help train many over the years! :)14:46
JoeRRP: Everyones crushed. Late stage capitalism at its best.14:47
JaMaRP: can you write this as official YP statement somewhere so I can point relevant people to it and they might take it more seriously than just me warning them that there is this manpower issue?14:51
*** yann <yann!> has joined #yocto14:52
*** tempoDrom <tempoDrom!555e4206@> has joined #yocto14:52
tempoDromHey peeps14:53
tempoDromIs it possible to expand a bitbake variable with a cli helper app?14:53
*** jobroe <jobroe!~manjaro-u@> has quit IRC14:53
JaMaRP: sometimes I also get an answer like "we're already funding the project"14:53
*** jobroe <jobroe!~manjaro-u@> has joined #yocto14:53
tempoDromSomething like (invented cli): "bitbake-expand DISTRO_VERSION"14:54
qschulztempoDrom: what is your issue exactly? (bitbake myrecipe -e | less could help you)14:54
RPJaMa: Its been mentioned at the governing meetings but yes, I think we can do something14:54
frayThe CLI can access variables.. (or so I thought)..  but it takes some effort to access the data store for the backend.14:55
fray(I am assuming this is a bitbake cli)14:55
tempoDromqschulz: Am trying to print some user friendly messages for the build users14:55
*** yacar_ <yacar_!> has joined #yocto14:55
LetoThe2ndtempoDrom: just make a "something" that internally calls bitbake -e and parses it.14:55
tempoDromLetoThe2nd: Guess that would work. Thanks :+1:14:56
JoeROoooh, fearsome bash script time ;-)14:56
qschulztempoDrom: if it's in a recipe, ina  specific task, use bb.warn() or something to print a message $VAR or d.getVar(VAR, true) if python. All depends what exactly you want to do and when14:57
LetoThe2ndJS! JS! you can do it in JS!14:57
tempoDromI have to make a "sales pitch" to a dev which thinks yocto is complicated. And just wants to have something like: ./build dev    or   ./build release14:58
tempoDromFrom whatever is the current git repo14:58
RPtempoDrom: you could also look at the tinfoil API14:59
JoeRI have it hooked under jenkins, one click for most people.14:59
* zeddii wants to reply to RP14:59
zeddiicrap, enter key ruined that joke14:59
frayahh yes, tinfoil, forgot the name of the API..14:59
zeddiiRP I was going to say, 18h to 12 seconds, is that the best you can do ?14:59
RPzeddii: :)14:59
qschulztempoDrom: well if you have two different images or distros for dev or release, it's still only one line :)15:00
RPzeddii: was amazingly hard to see why that script didn't work15:00
tempoDromSo would like to show THat's all good, but want to give some echoing of the basics that will be built15:00
tempoDromLike the DISTRO_VERSION and the IMAGE_NAME15:00
qschulzDISTRO_VERSION is already printed15:01
qschulzbitbake -e reparses all recipes, so it can take quite some time if you're doing it a lot15:02
LetoThe2ndtempoDrom: i'd go for kas + some nice config pretty-rpinting.15:02
tempoDromThat's true, but it's "hidden" within the other yocto related context which isn't important to whoever isn't doing yocto15:02
*** sagner <sagner!> has joined #yocto15:02
LetoThe2ndthen you get a container-contained build in one line with pretty whatevers. done.15:02
tempoDromLetoThe2nd: Don't know what kas is, checking....15:03
qschulztempoDrom: ugh... That's how we got dozens of warning messages. Because nobody reads them "it's just yocto"15:03
LetoThe2ndi take 10%, just so you know. plus a crate of beer.15:03
[Sno]JaMa: yes, around15:04
tempoDromqschulz: I'll check it for daily builds, but this is for them to build locally and confirm the changes they made didn't break the system15:04
qschulztempoDrom: teach them how to use Yocto. If they don't need it, I'd try to use a Yocto SDK so they don't have to care. Never used it though15:04
JoeRLetoThe2nd: Where do we ship this beer? Next Yocto-meet, for all the team? Or direct to you?15:04
LetoThe2ndJoeR: next yocto-meet of any form is fine. i'm happy to share.15:04
[Sno]RP: wrt. the make upgrade to 4.3 - I tried 2 setups with meta-mingw doing "bitbake core-image-mingw-sdktest && bitbake core-image-mingw-sdktest -c populate_sdk" - one musl+freescale/ls2088ardb and one glibc+intel/genericx86_6415:06
[Sno]RP: neither one breaks on make15:06
JaMa[Sno]: you seem to be using svn fetcher as you were touching it last, can you please check ?15:07
*** kpo <kpo!> has quit IRC15:07
*** kpo_ <kpo_!> has joined #yocto15:07
JaMa[Sno]: it's not caused by your change for sure, I'm just interestd if you're seeing the same15:07
RP[Sno]: did you try "bitbake nativesdk-make" ?15:07
[Sno]RP: did - builds fine :(15:08
RP[Sno]: ERROR: nativesdk-make-4.3-r0 do_configure: QA Issue: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities. was the error15:08
RP[Sno]: I guess we'll have to rerun and get the config.log, see what its complaining about15:09
[Sno]RP: can I have the log ?15:09
RP[Sno]: lost now, we'll have to rerun15:09
*** tempoDrom <tempoDrom!555e4206@> has quit IRC15:09
[Sno]I'm pretty sure I have something on my build server which interferes15:09
RP[Sno]: running15:10
*** ericch <ericch!> has joined #yocto15:10
[Sno]RP: thanks15:10
[Sno]JaMa: looks similar to my checkouts before my change ;) - except I used sth. like svn://;module=/src/target/gpio/trunk;path_spec=gpio15:11
*** WillMiles <WillMiles!~Will@> has joined #yocto15:12
*** mardy <mardy!> has joined #yocto15:12
JaMa[Sno]: can you try to build those 4 meta-oe recipes in your setup just to confirm it fail the same for you?15:13
[Sno]JaMa: sure - and I can dig deeper then - do I have to configure a special machine, or would qemuarm do?15:15
JaMaqemuarm should be fine15:15
JaMait's just to find out what might be the difference between our builders, because khem's world build seem to be fine15:16
JaMaand I doubt this was broken since thud (and there aren't many changes in svn fetcher since thud)15:16
[Sno]probable EU/US issue? :)15:16
JaMayou mean Trump is behind it?15:17
[Sno]I will look soon - before weekend15:17
*** comptroller <comptroller!> has quit IRC15:18
*** WillMiles <WillMiles!~Will@> has quit IRC15:20
*** comptroller <comptroller!> has joined #yocto15:20
*** WillMiles <WillMiles!~Will@> has joined #yocto15:24
RP[Sno]: grep for unsafe15:24
RP[Sno]: I know the build is still running but we have the log :)15:25
[Sno]it seems to add /usr/local/lib to -L - weird, smells - digging fot it15:26
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC15:30
*** [Sno] <[Sno]!> has quit IRC15:34
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto15:34
*** [Sno] <[Sno]!> has joined #yocto15:35
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto15:36
*** kovalevsky <kovalevsky!~kovalevsk@> has joined #yocto15:42
*** kovalevsky <kovalevsky!~kovalevsk@fedora/kovalevsky> has joined #yocto15:42
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC15:42
*** Zajc <Zajc!> has joined #yocto15:43
*** JoeR <JoeR!> has quit IRC15:45
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto15:45
*** TobSnyder <TobSnyder!~schneider@> has quit IRC15:54
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto15:54
*** RP <RP!> has quit IRC16:01
smurrayqschulz: re the discussion about externalsrc a while ago, I regularly use it via local.conf or site.conf and find the note about what is being built externally helpful even w/o using devtool (which I also do sometimes)16:02
*** pohly <pohly!> has quit IRC16:03
*** RP <RP!> has joined #yocto16:03
*** sagner <sagner!> has quit IRC16:04
JPEWsmurray: qschulz: Me too FWIW16:05
*** sagner <sagner!> has joined #yocto16:05
*** Sandrita <Sandrita!ade76a22@gateway/web/cgi-irc/> has joined #yocto16:06
*** ibinderwolf <ibinderwolf!> has quit IRC16:07
qschulzsmurray: via local.conf?16:07
*** gsalazar <gsalazar!> has joined #yocto16:07
smurrayqschulz: yeah, INHERIT += "externalsrc", EXTERNALSRC_pn-foo = "/path/foo"16:09
qschulzisnt' that extremely inefficient?16:17
qschulzcompared to devtool for example?16:17
qschulzbecause you're actually making all recipes inherit externalsrc and thus modify all recipes?16:17
qschulzwhat does it help you with that devtool cannot? Being curious here :)16:18
qschulzsmurray: ^16:18
*** AndersD <AndersD!~AndersD@2a02:aa1:1610:e47a:f41b:50ff:fecc:24cf> has joined #yocto16:19
*** jobroe <jobroe!~manjaro-u@> has quit IRC16:20
smurrayqschulz: 2 reasons: 1) in my experience devtool falls down sometimes when patches are spread across .inc and .bbappends  2) there are times (basically all the time with AGL) when I cannot share a build directory across different platform configurations, and futzing with devtool options to try to share a common workspace is too much hassle16:21
smurrayqschulz: I basically only ever use devtool if I know the recipe I'm running it against is simple and the change is a one-off.  I could be missing out, but I know externalsrc works16:22
*** vineela <vineela!vtummala@nat/intel/x-cmjqgrmdlrgkinzd> has joined #yocto16:23
qschulz1) only had issues with glibc (ah, that reminds me we still haven't worked that out with bluelightning :) ) and abuse in patchdir (patching files in the FS (well in WORKDIR) and not in the sources)16:23
qschulzI do not understand 2) (might be too late for my brain :) )16:23
smurrayqschulz: and I guess a 3rd one, it's been my experience that devtool is a non-starter with kernel trees, that's a common usecase for externalsrc16:24
qschulzsmurray: yup, debugged a few times the kernel with devtool, used manual compilation and tftp on my u-boot instead now, but that's a different process for sure. Could you explain 2)?16:26
qschulzbut I understand that this message should stay here :)16:26
*** yann <yann!> has quit IRC16:26
qschulzif you have time, it's just curiosity :)16:27
JPEWRP, kanavin_home: I pushed a fix for wayland with meson to meta-mingw/master-next16:27
smurrayqschulz: so AGL uses a script to generate the conf files, as it's known the BSP layers for different platforms won't interoperate.  That means the easiest way to test multiple platforms is to have different build directories, so I can't easily test a change made with "devtool modify" on more than one platform w/o mucking around more16:27
smurrayqschulz: I'm surprised devtool works on the kernel for you, last time I tried it failed spectacularly16:28
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto16:28
qschulzsmurray: gotcha.16:28
qschulzsmurray: well... it was maybe on krogoth. But definitely not something newer than thud. And we've our custom kernel recipe (no kernel-yocto inherited for example), so maybe that changes a few things16:29
qschulzI just remember the time required for devtool to unpack and decided after two devtool that I wouldn't do that again :)16:29
*** ericch <ericch!> has quit IRC16:29
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC16:31
*** ericch <ericch!> has joined #yocto16:31
RPJPEW: cool, thanks!16:31
*** opennandra <opennandra!> has quit IRC16:32
*** meego <meego!~meego@2001:41d0:fe7e:c800:f13a:a52:a21b:c077> has joined #yocto16:35
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto16:41
*** Bunio_FH <Bunio_FH!> has quit IRC16:41
RPJPEW: and then I promptly forget to set it :)16:51
*** dreyna <dreyna!> has joined #yocto16:52
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC16:52
*** yacar_ <yacar_!> has quit IRC16:52
*** yann <yann!> has joined #yocto16:57
RPJPEW: still fails: :(16:58
ningaubleOne thing I noticed happening is that if I bitbake -c menuconfig virtual/kernel, any subsequent 'bitbake <image>' continues to build the default kernel.  What's the step I'm missing to ensure my own config is built within the image?16:59
ningaubleI resolve it by manually copying the .../.meta/.../.config file into defconfig, but surely that's not the right way to do things.  :)17:00
*** gsalazar <gsalazar!> has quit IRC17:00
RPningauble: we've not come up with a good way to automate that step generically17:00
qschulzningauble: -c savedefconfig, then take the defconfig at the exact same place. That's one more step. Cleaner file but not cleaner process17:02
*** fl0v0 <fl0v0!~fvo@> has quit IRC17:02
ningaubleAh, right on, thank you.  So a followup question, and shame on me for not just trying this myself, but does devtool deploytarget virtual/kernel root@<target> work in theory?  If yes, any additional step for module deployment?17:03
*** gsalazar <gsalazar!> has joined #yocto17:03
ningaubleerr deploy-target, of course17:03
*** guerinoni <guerinoni!> has quit IRC17:04
*** m1ster_r0b0t <m1ster_r0b0t!> has joined #yocto17:04
*** vineela <vineela!vtummala@nat/intel/x-cmjqgrmdlrgkinzd> has quit IRC17:05
qschulzningauble: try and let us know :p I'd say if it works, it works only in one very specific case where the kernel is loaded in U-Boot from the rootfs. But I don't know anything about that, just making assumptions (I don't see devtool knowing where to flash the kernel)17:06
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC17:07
JPEWRP: Hmm, I fixed that bug...17:07
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC17:07
JPEWAh, right I fixed it in autotools... not meson :(17:07
tlwoernersadly, YP didn't make the cut for GSoC this time :c17:15
*** jani191 <jani191!> has joined #yocto17:16
jani191I'm working with NXP iMX8QXPMEK evaluation board.  I downloaded bsp release L4.19.35_1.1.0_MX8QXP from following site:17:16
jani191This bsp release is for Yocto Project 2.7 (Warrior)17:16
jani191I built yocto project for this bsp release.  I copied built image into sd card and then booted NXP board from sd card.  I need to step through USB Host Subsystem source code running in embedded linux kernel?17:16
jani191There is a serial connection between my NXP evaluation board and my PC.  Micro-USB Debug port in NXP board is connected to USB port in my PC.  How do I setup debugging environment so I can see source code and symbols17:16
jani191running in my NXP board?17:16
qschulzjani191: define "USB Host Subsystem"17:16
paulbarkerjani191: That's probably easier for NXP to answer than for us here17:17
qschulzif you're planning in debugging the kernel, I suggest the awesome slides:
jani191qschulz:  The kernel code that is part of Linux image created by yocto project has several subsystems.  One of them is USB subsystem.17:18
qschulzjani191: so the actual question is how do I debug a kernel. It being built with Yocto isn't going to matter I'm afraid. You can contact NXP as paulbarker suggested or join the appropriate IRC chan for NXP kernels17:19
jani191qschulz:  Please let me clarify.  I need to setup my debug / development environment.17:20
jani191I don't even know if there is any problem with kernel.  Maybe I shouldn't say that I need to debug kernel.   I just need to setup17:21
jani191debug environment.17:21
tlwoernerjani191: add gdbserver to your target image17:22
jani191tlwoerner:  Is there a way to check if gdbserver is already in my target image?17:23
paulbarkerjani191: I recommend starting with the project documentation at
paulbarkerDebugging remotely using gdb is covered there:
tlwoernerjani191: if you enabled buildhistory you can look in ${buildfolder}/buildhistory/images/${machine}/${clibrary}/${image}/installed-packages.txt17:25
tlwoernerpaulbarker: ooh, that's good. i went looking for that recently and didn't find it. and i see some of the wording could use some tweaking ;-)17:28
*** meego <meego!~meego@2001:41d0:fe7e:c800:f13a:a52:a21b:c077> has quit IRC17:29
jani191tlwoerner:  Inside ${buildfolder} there isn't buildhistory folder.  I see following folders inside ${buildfolder}, cache, conf, sstate-cache, and tmp17:29
tlwoerneri was going to blog about that too, but now i have more ideas. ideally i'd like to see devtool help out with this :-)17:29
tlwoernerjani191: just means you havent' enabled buildhistory17:29
jani191tlwoerner:  How do I enable buildhistory?17:29
*** vineela <vineela!~vtummala@> has joined #yocto17:30
jani191tlwoerner:  OK. thank you!17:30
jani191paulbarker:  Thank you!17:30
*** ningauble <ningauble!> has quit IRC17:30
jani191qschulz:  thank you for having me clarify the question.17:31
Saurjani191: You do not need to enable buildhistory to get a list of packages that went into an image. You can find it as tmp/deploy/images/<machine>/<image name>-<machine>.manifest17:33
*** vmeson <vmeson!> has quit IRC17:34
*** AndersD <AndersD!~AndersD@2a02:aa1:1610:e47a:f41b:50ff:fecc:24cf> has quit IRC17:36
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC17:37
*** AndersD <AndersD!~AndersD@2a02:aa1:1610:e47a:f41b:50ff:fecc:24cf> has joined #yocto17:37
*** ningauble <ningauble!> has joined #yocto17:38
Saurjani191: For some more information per package about what went into the image you can also do: oe-pkgdata-util -p tmp/pkgdata/<machine> package-info -f tmp/deploy/images/<machine>/<image name>-<machine>.manifest17:38
jani191Saur:  I have <image name>-<machine>.manifest open.  Do I search for gdbserver in this file?17:39
Saurjani191: Yes17:39
*** goliath <goliath!> has quit IRC17:44
jani191Saur:  I searched for gdbserver in <image name>-<machine>.manifest but didn't find it.  When I typed oe-pkgdata-util command, I got command not found17:45
jani191Can I run oe-pkgdata-util command from anywhere?17:46
Saurjani191: No, from an initiated build environment, i.e., same as where you run bitbake.17:47
*** tomeccles <tomeccles!~tomeccles@> has quit IRC17:48
Saurjani191: Or technically, you can run it from anywhere if you specify the -p option as I did, but if the environment isn't initialized, then you need to give the full path to the oe-pkgdata-util script.17:48
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto17:48
Saurjani191: And the relative tmp/ paths also assumed that you were in the build directory.17:49
jani191Saur:  I sent command from ${buildfolder}.  I get:    oe-pkgdata-util:  command not found17:53
Saurjani191: Typically you add tools-debug to EXTRA_IMAGE_FEATURES in your local.conf if you want to have gdbserver installed in the image.17:53
jani191Saur:  In my local.conf, EXTRA_IMAGE_FEATURES ?= "debug-tweaks"17:55
Saurjani191: Yes. Change it to: EXTRA_IMAGE_FEATURES ?= "debug-tweaks debug-tools"17:55
Saurjani191: That should give you gdb, gdbserver, strace17:56
jani191Saur:  Thank you very much!  I will rebuild yocto project.17:57
champagneghi, how do I install /lib/modules/$(kernel)/build/ in a kernel image to use systemtap with it? I thought adding kernel-dev would do it.18:03
*** sagner <sagner!> has quit IRC18:04
*** dreyna_ <dreyna_!~dreyna@2601:646:4201:b1a0:49a4:e792:1fcb:7c70> has joined #yocto18:13
*** dreyna <dreyna!> has quit IRC18:17
*** maudat <maudat!~moda@> has quit IRC18:23
*** frsc <frsc!> has quit IRC18:25
*** vmeson <vmeson!~rmacleod@> has joined #yocto18:27
*** yann <yann!> has quit IRC18:30
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has quit IRC18:32
*** AndersD <AndersD!~AndersD@2a02:aa1:1610:e47a:f41b:50ff:fecc:24cf> has quit IRC18:35
*** vineela <vineela!~vtummala@> has quit IRC18:46
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto18:48
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto18:49
JPEWRP, kanavin_home: Already I sent a patch to meson.bbclass that fixes MinGW (tested it this time :)18:52
JPEWI'm not sure if it's the "right" fix, so let me know what you think18:52
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC18:55
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:59
*** matthewzmd <matthewzmd!~user@> has joined #yocto19:05
*** geheimnis` <geheimnis`!~geheimnis@> has quit IRC19:11
*** sagner <sagner!~ags@2a02:169:3df5::587> has joined #yocto19:18
*** gsalazar <gsalazar!> has quit IRC19:18
*** geheimnis` <geheimnis`!~geheimnis@> has joined #yocto19:20
*** opennandra <opennandra!> has joined #yocto19:23
LetoThe2ndok folks. now for something completely different (and almost serious): for $reasons YÖP seems to have massive lack in dev hours to even fix simple stuff.19:31
LetoThe2ndso who's in, if i announce to donate 5€ for every new contriutor that fixes an item of the newcomer bug list?19:31
*** Sandrita <Sandrita!ade76a22@gateway/web/cgi-irc/> has quit IRC19:35
*** yann <yann!> has joined #yocto19:36
*** dreyna__ <dreyna__!> has joined #yocto19:37
vmesonJPEW: matthewzmd got help with his perl problem. matthewzmd explain how to run one perl test in the bugzilla entry please.19:39
*** ningauble <ningauble!> has quit IRC19:40
*** dreyna_ <dreyna_!~dreyna@2601:646:4201:b1a0:49a4:e792:1fcb:7c70> has quit IRC19:41
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto19:41
JPEWvmeson: matthewzmd: OK, good :)19:42
*** matman <matman!268c1a9c@> has joined #yocto19:44
*** matman is now known as matman112219:45
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC19:48
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC19:49
matman1122Has anyone used the the yocto conan layer?19:49
LetoThe2ndmatman1122: not yet, but it sounds interesting. needs a closer look at their fetching stage, though!19:51
*** opennandra <opennandra!> has quit IRC19:55
paulbarkerOh gods another language-specific package manager19:58
paulbarkerSearching "license compliance" in their docs gives zero results19:59
LetoThe2ndpaulbarker: very good point.19:59
paulbarkerThis is my drum and I'll keep banging it20:00
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC20:01
smurrayI assume it's a JFrog project with the aim being to have you sign up for Artifactory?20:01
paulbarker - do_install is the correct step to fetch from the network right?20:03
paulbarkerI'm in a facetious mood today20:03
LetoThe2ndpaulbarker: that why i said one needs to look at the fetch stage. *plonk* it is, then.20:04
*** gsalazar <gsalazar!> has joined #yocto20:04
neverpanicIsn't conan a tool to install precompiled binaries?20:07
* tgamblin wonders what is best in life20:08
LetoThe2ndtgamblin: beer + heavy metal.20:08
matthewzmdtgamblin: + emacs20:08
paulbarkerneverpanic: Looks like it. Still should be doing network access in do_fetch and providing some way to distribute source alongside binaries for copyleft stuff20:08
neverpanicSo if I change my optimization flags in my distro conf packages downloaded by conan will just ignore that? Not sure if that's a tool I want.20:12
*** matthewzmd <matthewzmd!~user@> has quit IRC20:19
paulbarkerneverpanic: You're probably not their intended audience. Neither am I20:20
*** hpsy <hpsy!~hpsy@> has quit IRC20:22
smurrayheh, I see no metadata about who has built the binaries on and there's no mention of signing anywhere20:23
smurrayseems a bit of a nightmare20:24
*** matthewzmd <matthewzmd!~user@> has joined #yocto20:25
*** vineela <vineela!~vtummala@> has joined #yocto20:34
*** nerdboy <nerdboy!~sarnold@> has joined #yocto20:38
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto20:38
*** goliath <goliath!> has joined #yocto20:39
*** gsalazar <gsalazar!> has quit IRC20:40
*** gsalazar <gsalazar!> has joined #yocto20:41
*** gsalazar <gsalazar!> has quit IRC20:45
*** vmeson <vmeson!~rmacleod@> has quit IRC20:46
*** gsalazar <gsalazar!> has joined #yocto20:48
*** john12365 <john12365!836b93fc@> has joined #yocto20:54
*** tgamblin <tgamblin!~tgamblin@> has quit IRC21:03
*** berton <berton!~berton@> has quit IRC21:15
jani191I'm working with NXP iMX8QXPMEK evaluation board.  I downloaded bsp release L4.19.35_1.1.0_MX8QXP from following site:21:32
jani191This bsp release is for Yocto Project 2.7 (Warrior)21:32
jani191While back, I built yocto project for this bsp release. Today I made one line change to local.conf file.  To rebuild image, do I need to:                         DISTRO=<distro name> MACHINE=<machine name> source -b <build dir>21:32
jani191or do I just:   bitbake <image name>21:34
JPEWjani191: It depends; if you already have the build environment sourced in your shell, the latter. Otherwise the former21:35
JPEWI would guess at any rate. I'm not familiar with that specific BSP21:36
jani191JPEW:  I only added "debug-tools" to EXTRA_IMAGE_FEATURES in local.conf file.  Do I need to source build environment again?21:37
*** dreyna__ <dreyna__!> has quit IRC21:38
JPEWjani191: You should only need to source the environment once in a given shell session21:39
JPEWSo, if you already have done that in your current shell, no21:39
JPEWChanges in local.conf don't require you to re-setup the environment. bitbake will detect the change and reparse21:40
jani191JPEW:  ok thank you!21:41
jani191$  source setup-environment <build_dir>                           My <build_dir> is just build              setup_environment is one level above build21:44
jani191What should be exact command21:44
jani191to setup environment script21:44
JPEWjani191: Probably `source setup-environment build`, but again I'm not familiar with that specific BSP21:49
JPEWTry it and see what happens :)21:49
*** gsalazar <gsalazar!> has quit IRC21:50
jani191JPEW:  I did  'source setup-environment ./build'.  It basically says I can run bitbake <target>.  It says "Your configuration files at ./build have not been touched."  It looks like it didn't do anything because there was nothing to do.21:53
*** yann <yann!> has quit IRC21:53
JPEWSounds reasonable21:54
JPEWThats what I would expect from a well behaved SDK :)21:54
*** gsalazar <gsalazar!> has joined #yocto21:55
JPEWjani191: Your local configuration for the build are the files in build/conf/. You worked hard to created those files! you don't want the SDK to overwrite them because you re-sourced the build environment ;)21:57
jani191JPEW:  I just want to be clear that I'm not building SDK.  I'm re-building yocto project.21:59
JPEWjani191: Ya sorry, I meant BSP22:00
jani191JPEW:  Thanks again.22:00
JPEWjani191: Some vendors package up Yocto with some scripts and call it an "SDK"22:00
JPEWsome call it a "BSP", just depends on the vendor22:03
jani191I added 'debug-tools' to my local.conf file, and now I cannot re-build image using yocto project:                                    ERROR: Nothing PROVIDES 'core-image-minimal'22:12
jani191core-image-minimal was skipped: 'debug-tools' in IMAGE_FEATURES (added via EXTRA_IMAGE_FEATURES) is not a valid image feature. Valid features: allow-empty-password allow-root-login dbg-pkgs debug-tweaks dev-pkgs doc doc-pkgs eclipse-debug empty-root-password hwcodecs nfs-client nfs-server package-management post-install-logging ptest-pkgs22:12
jani191qtcreator-debug read-only-rootfs splash src-pkgs ssh-server-dropbear ssh-server-openssh staticdev-pkgs tools-debug tools-profile tools-sdk tools-testapps x11 x11-base x11-sato22:12
JPEWjani191: I think the one you are looking for might be "tools-debug" ?22:15
jani191JPEW:  That was it!  Thank for that.  Now it's building.22:19
*** falstaff <falstaff!~quassel@> has quit IRC22:19
*** gsalazar <gsalazar!> has quit IRC22:23
*** stacktrust <stacktrust!> has quit IRC22:26
*** sdude <sdude!cb1f2c1e@> has joined #yocto22:27
*** RP <RP!> has quit IRC22:28
*** RP <RP!> has joined #yocto22:33
sdudeHi, any idea how I need to refer to a header file located in /usr/include/uapi/linux/ of a linux-stable recipe so that it ends up in the SDK?22:38
*** tgamblin <tgamblin!> has joined #yocto22:39
*** kovalevsky <kovalevsky!~kovalevsk@fedora/kovalevsky> has quit IRC22:45
RPhmm, my irc client is not happy today :(22:46
*** jani191 <jani191!> has quit IRC22:49
JPEWRP: Not having much luck with the communication channels today22:52
RPJPEW: no :(22:53
*** comptroller <comptroller!> has quit IRC22:55
*** comptroller <comptroller!> has joined #yocto22:59
*** WillMiles <WillMiles!~Will@> has quit IRC23:00
*** gep <gep!~gep@> has joined #yocto23:27
*** stacktrust <stacktrust!> has joined #yocto23:28
*** leon-anavi <leon-anavi!~Leon@> has quit IRC23:30
*** rburton <rburton!rburton@nat/intel/x-tqsxnmzendaewftp> has quit IRC23:30
*** vmeson <vmeson!> has joined #yocto23:33
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC23:47

Generated by 2.17.2 by Marius Gedminas - find it at!