Thursday, 2021-01-14

*** sesom <sesom!> has joined #yocto00:00
*** sesom <sesom!> has quit IRC00:04
* RP -> Zzzz00:06
*** sakoman <sakoman!> has joined #yocto00:08
*** sesom <sesom!> has joined #yocto00:08
*** sesom <sesom!> has quit IRC00:09
*** sesom <sesom!> has joined #yocto00:10
sgwhalstead: do I still have an AB account that's active?  If so, I probably need a password reset00:10
halsteadsgw, For running builds? I'll check.00:11
*** sesom <sesom!> has quit IRC00:11
*** sesom <sesom!> has joined #yocto00:12
*** sesom_ <sesom_!> has joined #yocto00:13
*** sesom_ <sesom_!> has quit IRC00:14
halsteadsgw, PM sent.00:15
*** sesom <sesom!> has joined #yocto00:15
*** sesom <sesom!> has quit IRC00:16
*** sesom_ <sesom_!> has joined #yocto00:16
*** sesom_ <sesom_!> has quit IRC00:18
*** sesom <sesom!> has joined #yocto00:18
*** sesom <sesom!> has quit IRC00:19
*** sesom <sesom!> has joined #yocto00:20
*** sesom <sesom!> has quit IRC00:21
*** sesom_ <sesom_!> has joined #yocto00:21
*** sesom <sesom!> has joined #yocto00:23
*** sesom <sesom!> has quit IRC00:24
*** sesom <sesom!> has joined #yocto00:25
*** sesom <sesom!> has quit IRC00:29
*** sesom <sesom!> has joined #yocto00:34
*** B0ned1ger <B0ned1ger!> has quit IRC00:36
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto00:36
*** sakoman <sakoman!> has quit IRC00:38
*** sesom <sesom!> has quit IRC00:38
paulgis kernel v5.4 + rootfs from fall 2020 a combo we (yocto) still care about?  (normal default is v5.8 kernel)00:40
*** sesom <sesom!> has joined #yocto00:41
paulgA systemd change from late August 2020 doesn't play nice with kernels older than v5.8 and I'm wondering whether to send the (systemd) fix....00:42
*** sesom <sesom!> has quit IRC00:43
*** sesom <sesom!> has joined #yocto00:44
*** sesom_ <sesom_!> has joined #yocto00:45
*** sesom_ <sesom_!> has quit IRC00:47
*** sesom <sesom!> has joined #yocto00:47
*** sesom <sesom!> has quit IRC00:48
*** sesom_ <sesom_!> has joined #yocto00:49
*** sesom_ <sesom_!> has quit IRC00:50
*** sesom <sesom!> has joined #yocto00:50
*** sesom <sesom!> has quit IRC00:54
*** sakoman <sakoman!~steve@> has joined #yocto00:55
*** linums <linums!~linums@> has quit IRC00:59
*** linums <linums!> has joined #yocto00:59
*** sesom <sesom!> has joined #yocto01:00
*** sesom <sesom!> has joined #yocto01:01
*** sesom <sesom!> has quit IRC01:05
*** linums <linums!> has quit IRC01:09
*** linums <linums!~linums@> has joined #yocto01:09
*** sakoman <sakoman!~steve@> has quit IRC01:09
*** yizhao <yizhao!~zhaoyi@> has quit IRC01:12
*** yizhao <yizhao!~zhaoyi@> has joined #yocto01:13
*** sesom <sesom!> has joined #yocto01:21
*** sesom <sesom!> has quit IRC01:26
*** sakoman <sakoman!> has joined #yocto01:26
*** sesom <sesom!> has joined #yocto01:27
*** sesom <sesom!> has quit IRC01:31
*** sesom <sesom!> has joined #yocto01:31
*** yizhao <yizhao!~zhaoyi@> has quit IRC01:33
*** yizhao <yizhao!~zhaoyi@> has joined #yocto01:34
*** sesom <sesom!> has quit IRC01:35
*** sesom <sesom!> has joined #yocto01:39
*** rcw <rcw!~rcwoolley@> has quit IRC01:40
*** sesom <sesom!> has quit IRC01:41
*** sesom <sesom!> has joined #yocto01:41
*** sesom <sesom!> has quit IRC01:43
*** sesom_ <sesom_!> has joined #yocto01:43
*** linums <linums!~linums@> has quit IRC01:44
*** linums <linums!> has joined #yocto01:44
*** sesom_ <sesom_!> has quit IRC01:44
*** sesom <sesom!> has joined #yocto01:45
*** sesom <sesom!> has quit IRC01:46
*** sesom_ <sesom_!> has joined #yocto01:46
*** sesom_ <sesom_!> has quit IRC01:48
*** sesom <sesom!> has joined #yocto01:48
*** sesom <sesom!> has joined #yocto01:50
*** sesom_ <sesom_!> has joined #yocto01:51
*** sesom_ <sesom_!> has quit IRC01:53
*** sesom <sesom!> has joined #yocto01:53
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:54
*** sesom <sesom!> has quit IRC01:54
*** sesom <sesom!> has joined #yocto01:54
*** sesom <sesom!> has quit IRC01:56
*** sesom_ <sesom_!> has joined #yocto01:56
khempaulg:  I thought it was only seen in KDE01:58
*** sesom_ <sesom_!> has quit IRC01:58
*** sesom <sesom!> has joined #yocto01:58
khembut regardless we should fix it in dunfell01:58
khemat the least01:58
khemoh we may not have that new systemd in dunfell01:58
paulgyea,  I'm not sure - was hoping someone else had better track of things in their head.02:02
paulg        <---- issue02:02
paulg      <--- my fix.02:02
*** sesom <sesom!> has quit IRC02:03
*** linums <linums!> has quit IRC02:05
*** linums <linums!~linums@> has joined #yocto02:05
*** sesom <sesom!> has joined #yocto02:08
*** sesom <sesom!> has quit IRC02:13
*** sesom <sesom!> has joined #yocto02:13
*** sesom <sesom!> has quit IRC02:18
*** sesom <sesom!> has joined #yocto02:18
*** sesom_ <sesom_!> has joined #yocto02:19
*** sesom_ <sesom_!> has quit IRC02:22
*** sesom <sesom!> has joined #yocto02:23
opellokhem: hi, in meta-qt5 d0cd7a7a70d3fe3b3041d41391c5c082d8f23a0d QMAKE_CFLAGS_ISYSTEM was removed to "Fix errors" but it seems handy to suppress warnings in qt headers?02:26
*** sesom <sesom!> has quit IRC02:27
*** sesom <sesom!> has joined #yocto02:28
opello(i didn't look in the patch, i see the include_next detail now :()02:28
*** sesom <sesom!> has quit IRC02:32
paulgany known current issues with mailing lists?   I'm getting...02:35
paulg550 5.1.1.   poky wasn't found at
*** B0ned1ger2 <B0ned1ger2!> has quit IRC02:36
*** B0ned1ger <B0ned1ger!> has joined #yocto02:36
paulg(trying to send another fix, not the systemd crap above)02:37
*** sesom <sesom!> has joined #yocto02:39
*** sesom <sesom!> has quit IRC02:41
*** sesom_ <sesom_!> has joined #yocto02:41
*** sesom_ <sesom_!> has quit IRC02:43
*** sesom <sesom!> has joined #yocto02:43
*** sesom <sesom!> has quit IRC02:48
smurraypaulg: some classic Lennart rationalization in that systemd issue...sigh02:56
paulgno kidding eh?   kind of dripping with "My way or the highway.".02:56
paulgUser input?  Bah, who cares about that.02:57
smurrayI guess he's not heard of LTS kernels02:57
*** sesom <sesom!> has joined #yocto03:03
*** tlwoerner <tlwoerner!~tlwoerner@unaffiliated/tlwoerner> has quit IRC03:06
*** kaspter <kaspter!~Instantbi@> has quit IRC03:08
*** kaspter <kaspter!~Instantbi@> has joined #yocto03:09
smurraypaulg: there's a plan to set up a "next" branch in AGL to track poky master while AGL master stays on dunfell, I suspect there's a couple of platforms with BSP layers where we'd see the issue03:10
*** tlwoerner <tlwoerner!~tlwoerner@unaffiliated/tlwoerner> has joined #yocto03:11
*** sesom <sesom!> has quit IRC03:11
smurraypaulg: but we might end up just testing with qemu* for the interim, it's not clear to me yet03:12
paulgI tested it on v5.4 to ensure it fixes the issue there; once I test on v5.8+ to ensure it doesn't somehow break things there, I'll probably just send it along.03:15
paulgAt least that way, anyone impacted can (in theory) find it via google w/o rewriting their own fix.03:15
*** yizhao <yizhao!~zhaoyi@> has quit IRC03:19
*** yizhao <yizhao!~zhaoyi@> has joined #yocto03:22
*** ahadi <ahadi!> has quit IRC03:27
*** ahadi <ahadi!~ahadi@> has joined #yocto03:29
*** sesom <sesom!> has joined #yocto03:48
*** sesom <sesom!> has quit IRC03:54
*** sesom_ <sesom_!> has joined #yocto03:54
*** [Sno] <[Sno]!> has joined #yocto03:57
*** sesom_ <sesom_!> has quit IRC03:59
*** sno <sno!> has quit IRC03:59
zeddiias much as I like the ability to manage all my mailing lists via gmail. Dear lord the threading is so broken it is shocking.04:02
paulgthat and the random lkml mails that get tossed in spam for no apparent reason.04:08
zeddiithe only way to dig replied patches, or v2, etc out of the threads, is to use imap and mutt04:09
zeddiiwhich is ok, since I don't mind that, but I occasionally miss that there's a new version completely.04:09
zeddii(yes, I know there are tools that can help with this)04:09
paulgvarious kernel people are using this "b4" thing which I've never really looked into yet.  Smells like an interface to lore.kernel.org04:13
zeddiiyah. I remember reading some thread about greg claiming it was the cat's ass04:14
zeddiiI should try it, since really, just that intro is what I end up doing with sorting in mutt, etc.04:14
paulgI don't merge dumptruck loads of poo from other people, so it probably isn't for me.04:14
zeddiii don't have that much volume either, but if I let things soak on the list for more than a couple days, things get tied into knots quickly04:15
*** sesom <sesom!> has joined #yocto04:15
zeddiibut the msg-id thing is the problem. I wonder if it can be adapted to non-lore use cases04:15
paulgNFI, but probably warrants a casual drive-by snoop to see.04:16
zeddiiyup.  I'll put it on my "I can't believe covid arrest has made me so desperate to look into this" list.04:17
paulgI would hope it would work on any standard mbox input, given that is what lore wants to hand out.04:17
paulgheh.  CDS  -  Covid defeat syndrome.04:17
paulgI powered up an old beagleboard-xM  ;  pretty sure I can chalk that up to CDS.04:18
zeddiiyup. I put linux on my 2008 macbook, so I could run home automation on it. that's my low bar so far.04:20
paulgCDS  -- Covid Desparation Syndrome.    Sounds better than "defeat".04:21
zeddiiyah, but kind of like how novel coronavrus sars v<whatever> causes covid, it should be that IPI-2k2 causes it.04:23
zeddii(incompetent politician infection 202x)04:23
paulgI mucked with dd-wrt on some ancient router e-waste semi-recently ; that was also 100% due to CDS.04:26
*** vineela <vineela!~vtummala@> has quit IRC04:28
*** sakoman <sakoman!> has quit IRC04:29
paulgI wonder what that says about the fact that I touched systemd code for the 1st time ever today?04:29
zeddiithat's probably lower04:30
paulgSomebody pass me the bleach and steel wool.04:30
paulgNeed to see if I can get that stink off me.04:30
*** goliath <goliath!> has quit IRC04:30
zeddiiheh. my plan is to stand up now and watch netflix, if there's anything I haven't seen yet :D04:31
paulgBridges of Madison County is still there waiting for you.04:31
*** B0ned1ger <B0ned1ger!> has quit IRC04:36
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto04:36
*** kpo_ <kpo_!> has quit IRC05:02
*** vineela <vineela!~vtummala@> has joined #yocto05:03
*** kpo_ <kpo_!> has joined #yocto05:03
*** sesom <sesom!> has quit IRC05:16
*** sesom_ <sesom_!> has joined #yocto05:16
*** vineela <vineela!~vtummala@> has quit IRC05:16
*** sesom_ <sesom_!> has quit IRC05:19
*** sesom <sesom!> has joined #yocto05:19
*** dreyna <dreyna!> has quit IRC05:21
*** yizhao <yizhao!~zhaoyi@> has quit IRC05:56
*** yizhao <yizhao!~zhaoyi@> has joined #yocto05:57
*** ahadi <ahadi!~ahadi@> has quit IRC06:03
*** ahadi <ahadi!~ahadi@> has joined #yocto06:05
*** beneth <beneth!> has joined #yocto06:08
*** sesom <sesom!> has quit IRC06:12
*** jobroe <jobroe!> has joined #yocto06:13
*** sesom <sesom!> has joined #yocto06:15
*** alessioigor <alessioigor!> has joined #yocto06:19
*** sesom <sesom!> has quit IRC06:20
*** alessioigor <alessioigor!> has quit IRC06:32
*** AndersD <AndersD!> has joined #yocto06:38
*** minimaxwell <minimaxwell!> has joined #yocto06:39
*** dreyna <dreyna!~dreyna@2601:646:4201:e280:dc48:5bae:ac10:1eb> has joined #yocto06:41
*** AndersD_ <AndersD_!> has joined #yocto06:42
*** linums <linums!~linums@> has quit IRC06:44
*** AndersD <AndersD!> has quit IRC06:44
*** linums <linums!> has joined #yocto06:45
*** dreyna <dreyna!~dreyna@2601:646:4201:e280:dc48:5bae:ac10:1eb> has quit IRC06:46
*** sesom <sesom!> has joined #yocto06:49
*** sesom <sesom!> has quit IRC06:54
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto07:15
*** linums <linums!> has quit IRC07:16
*** linums <linums!~linums@> has joined #yocto07:16
*** linums <linums!~linums@> has quit IRC07:20
*** linums <linums!~linums@> has joined #yocto07:21
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto07:24
*** ant__ <ant__!> has quit IRC07:25
*** kaspter <kaspter!~Instantbi@> has quit IRC07:29
*** kaspter <kaspter!~Instantbi@> has joined #yocto07:31
*** frsc <frsc!> has joined #yocto07:39
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto07:46
*** sesom <sesom!> has joined #yocto07:46
*** mckoan|away is now known as mckoan07:48
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto07:53
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/> has joined #yocto07:54
*** fl0v0 <fl0v0!~fvo@> has joined #yocto08:00
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto08:02
*** sgw <sgw!> has quit IRC08:11
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:b52d:d2b0:a399:9b05> has joined #yocto08:17
*** luneff <luneff!~yury@> has joined #yocto08:19
*** sesom <sesom!> has quit IRC08:27
*** camus1 <camus1!~Instantbi@> has joined #yocto08:27
*** sesom <sesom!nucatus@gateway/vpn/protonvpn/nucatus> has joined #yocto08:28
*** kaspter <kaspter!~Instantbi@> has quit IRC08:28
*** camus1 is now known as kaspter08:28
*** B0ned1ger2 <B0ned1ger2!> has quit IRC08:36
*** B0ned1ger <B0ned1ger!> has joined #yocto08:36
*** yann <yann!~yann@> has quit IRC08:37
*** sgw <sgw!> has joined #yocto08:51
*** manuel1985 <manuel1985!~manuel@> has joined #yocto08:55
*** codysch[m] <codysch[m]!codyschmat@gateway/shell/> has quit IRC09:00
*** sesom_ <sesom_!> has joined #yocto09:02
*** sesom <sesom!nucatus@gateway/vpn/protonvpn/nucatus> has quit IRC09:06
*** Sponge5 <Sponge5!> has joined #yocto09:12
*** RobertBerger <RobertBerger!> has joined #yocto09:13
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto09:33
*** dreyna <dreyna!> has joined #yocto09:34
*** yann <yann!~yann@> has joined #yocto09:37
Sponge5I've put a patch and a .bbappend in a custom layer, but bitbake doesn't find the patch, he looks for it only in the original layer, how can I fix that?09:45
mckoanSponge5: first of all tect with bitbake-layers show-overlayed09:47
OutBackDingosounds like a naming issue.... i put bbappends in custom-layers all the time09:48
Sponge5I might be missing something in layer.conf?09:49
Sponge5mckoan: what am I looking for with that command?09:49
Sponge5mckoan: my .bbappend?09:49
mcfriskSponge5: maybe FILESEXTRAPATHS_prepend := "${THISDIR}/files:" in the bbappend?09:49
mckoanSponge5: you should see that bbappend is taken into account09:49
mckoanmcfrisk: that's the second frequent mistake09:50
mckoanSponge5: pastebin-ing the bbappend would help a lot09:50
Sponge5mcfrisk: done that, except with ${PN}09:50
Sponge5BBPATH .= ":${LAYERDIR}" and BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"09:52
OutBackDingowhats the name of thefile for the  .bbappend09:53
Sponge5are in my layer.dir09:53
Sponge5OutBackDingo: nss_3.51.109:53
Sponge5OutBackDingo: nss_3.51.1.bbappend09:53
Sponge5OutBackDingo: it matches nss_3.51.1.bb09:54
OutBackDingommmm or nss_3.51.%.bbappend09:55
Sponge5bitbake finds the bbappend, it doesn't see the patch that's in the same directory as the bbappend09:55
mckoanSponge5: can you see it with bitbake-layers show-appends ?09:55
Sponge5mckoan: no09:56
Sponge5so it doesn't see the bbappend? :D09:56
mckoanSponge5: therefore bitbake doesn't find the bbappend09:56
mckoanbitbake-layers show-appends09:56
Sponge5then why would it try to build nss-native-3.51.1-r0.rpipatch109:57
mckoanwe need more details09:57
Sponge5Could you give me a resource for creating layers? I followed and it doesn't work for me09:58
mcfriskif bitbake -e output doesn't show the bbappend file, then layer config isn't correct. if it does, something else is wrong.09:59
Sponge5mcfrisk: It doesn't10:01
*** sesom_ <sesom_!> has quit IRC10:05
mckoanSponge5: bitbake-layers create-layer10:06
*** sesom <sesom!> has joined #yocto10:08
*** stuom1 <stuom1!> has joined #yocto10:09
stuom1is there some undocumented changes to ptest? I have ptest in DISTRO_FEATURES_append and ptest-pkgs in EXTRA_IMAGE_FEATURES, and my recipes inherit ptest, but ptest packages are not build. All this worked in Thud but now not in Dunfell10:12
*** sesom <sesom!> has quit IRC10:12
rburtonNo, should work still10:13
stuom1trying to bitbake a my-recipe-ptest package gives nothing RPROVIDES error10:13
rburtonright, you build recipes, not packages10:13
rburtonso bitbake my-recipe10:13
stuom1I mean having IMAGE_INSTALL += "my-package-ptest" like wiki suggests, does not work anymore10:15
*** sgw1 <sgw1!> has joined #yocto10:15
stuom1and having ptest-pkgs in image features to build all ptest-enabled packages does not build anything10:15
rburtoni'd check that the distro features change is actually working, bitbake -e my-package|grep DISTRO_FEATURES=10:15
*** sgw <sgw!> has quit IRC10:16
RobertBerger@stuoam1: ptest packages should even be built by default. they should be in DISTRO_FEATURES, as rburton points out10:16
rburtonwell, depends on your distro setup10:16
Sponge5FYI my problem was this, should've googled instead of duckduckgo'd
stuom1@rburton hmm it is not in DISTRO_FEATURES but it is in POKY_DEFAULT_DISTRO_FEATURES, should that have some effect10:19
rburtonif its not in DISTRO_FEATURES then it doesn't have any affect10:19
rburtonbeing in POKY_DEFAULT_DISTRO_FEATURES just means that the poky default distro features include it, but you're obviously not using default poky10:20
stuom1ok thanks. What could override DISTRO_FEATURES_append = " ptest"?10:22
stuom1I would imagine that appends in every case10:22
rburtonthats what -e is for10:27
rburtonit will show you how DISTRO_FEATURES is evaluated, and importantly will show you if your assignment is being overridden, or not being parsed at all10:28
*** linums <linums!~linums@> has quit IRC10:32
*** dreyna <dreyna!> has quit IRC10:32
*** stuom1 <stuom1!> has quit IRC10:33
*** stuom1 <stuom1!> has joined #yocto10:34
stuom1rburton hmm okay, it just shows one line of DISTRO_FEATURES, I'm not sure how to track it based on that information10:35
rburtondon't grep, write to a file and open it in less/your favourite editor10:36
rburtonabove the assignment is the history of the evaluation10:36
mckoanSponge5: great10:39
*** paulbarker_tmp <paulbarker_tmp!pbarkermat@gateway/shell/> has joined #yocto10:40
*** sesom <sesom!> has joined #yocto10:45
*** sesom <sesom!> has quit IRC10:52
*** iamnotyocto <iamnotyocto!59cd854e@> has joined #yocto10:54
*** sesom <sesom!> has joined #yocto10:58
*** sesom <sesom!> has quit IRC11:03
*** camus1 <camus1!~Instantbi@> has joined #yocto11:06
*** kaspter <kaspter!~Instantbi@> has quit IRC11:07
*** camus1 is now known as kaspter11:07
stuom1rburton thanks, Toradex new BSP had for some reason DISTRO_FEATURES_remove = "ptest"11:13
rburtonyeah that's dumb11:13
rburtonbecause you can't just reverse that with _append, remove wins11:13
*** iamnotyocto <iamnotyocto!59cd854e@> has quit IRC11:14
stuom1to their defense, it is commented with "TODO: review default distro features" :D11:15
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto11:16
*** RzR <RzR!~rzr@2a01:e35:2fd7:d710:5e08:ef32:68ac:50f9> has quit IRC11:17
*** RzR <RzR!~rzr@unaffiliated/rzr> has joined #yocto11:17
*** amerigo <amerigo!uid331857@gateway/web/> has joined #yocto11:23
qschulzstuom1: worst case scenario, you could suggest them to use what's "explained" in Chris's paragraph here:
RPthere appears to be a second repro bug in vulkan-samples :(11:46
*** stuom1 <stuom1!> has quit IRC11:47
*** sesom <sesom!> has joined #yocto11:51
*** sesom <sesom!> has quit IRC11:54
*** sesom <sesom!> has joined #yocto11:54
*** AndersD_ <AndersD_!> has quit IRC11:58
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:b52d:d2b0:a399:9b05> has quit IRC12:08
*** kpo_ <kpo_!> has quit IRC12:11
*** thekappe <thekappe!c65a42b1@> has joined #yocto12:11
*** kpo_ <kpo_!> has joined #yocto12:12
thekappehello guys.. I need a little help here.12:13
*** AndersD <AndersD!> has joined #yocto12:13
thekappeI have a device-tree append recipe that will compile system-top.dtb and copy it /boot/devicetree12:14
*** [Sno] <[Sno]!> has quit IRC12:14
thekappeIn order to that this recipe requires the do_configure task of the virtual/kernel12:14
thekappeon the other hand, the fitimage is generated by the virtual/kernel recipe12:14
thekappeand in order to have the fitimage with the dtb included I need to have the sytem-top.dtb in /boot/devicetree12:15
thekappeso there is like a circular dependency12:15
thekappeHow can I mange that so that the device-tree recipe fetches the kernel compiles the dtb and only after that the virtual/kernel recipe is run ?12:16
*** AndersD_ <AndersD_!> has joined #yocto12:16
*** AndersD <AndersD!> has quit IRC12:19
*** frsc <frsc!> has quit IRC12:24
*** oberstet <oberstet!~oberstet@> has joined #yocto12:24
*** sno <sno!> has joined #yocto12:29
*** frsc <frsc!> has joined #yocto12:36
*** sesom <sesom!> has quit IRC12:44
*** sesom <sesom!> has joined #yocto12:46
*** Chrys <Chrys!a5e14d1c@> has joined #yocto12:47
*** Chrys is now known as CptFooley12:48
*** sesom <sesom!> has quit IRC12:52
*** sesom <sesom!> has joined #yocto12:52
*** CptFooley <CptFooley!a5e14d1c@> has quit IRC12:53
*** CptFooley <CptFooley!a5e14d1c@> has joined #yocto12:53
*** CptFooley <CptFooley!a5e14d1c@> has quit IRC12:54
*** NiniC0c0 <NiniC0c0!> has joined #yocto12:57
*** Konsgn <Konsgn!> has joined #yocto13:01
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has joined #yocto13:01
*** NiniC0c096 <NiniC0c096!> has joined #yocto13:02
*** kaspter <kaspter!~Instantbi@> has quit IRC13:07
*** kaspter <kaspter!~Instantbi@> has joined #yocto13:07
*** luneff <luneff!~yury@> has quit IRC13:13
NiniC0c0Hi all:)  Stupid question : I have created a custom kernel module recipe (inherited from module). I have also a test-app. It's better to create a new recipe to build&install the app or i can add a task on the module inherited recipe ?13:14
*** JaMa <JaMa!> has joined #yocto13:17
Sponge5I've used devtool to create a patch, tested it out with bitbake, it worked, then commited and devtool update-recipe'd, now when I try to bitbake the whole thing I get a whole bunch of "Patching symbolic link..." and then "Patch ... does not apply", any ideas?13:23
Sponge5NiniC0c0: sounds like test-app is unrelated to the custom kernel module, so yes, separate recipe13:27
*** kaspter <kaspter!~Instantbi@> has quit IRC13:38
*** kaspter <kaspter!~Instantbi@> has joined #yocto13:39
*** kpo_ <kpo_!> has quit IRC13:44
*** kpo_ <kpo_!> has joined #yocto13:44
*** sakoman <sakoman!> has joined #yocto13:47
*** mcfrisk <mcfrisk!> has quit IRC13:52
*** mcfrisk <mcfrisk!> has joined #yocto13:52
*** kaspter <kaspter!~Instantbi@> has quit IRC14:24
thekappehello guys14:25
thekappeI'am facing a strange behaviour.. I've compiled  a whole distro14:25
thekappeburned on sd card and boot14:26
thekappethe strange thing is that the kernel boots, the filesystem is mount but I don't get any login prompt14:26
thekappeso I tried to nfs boot14:26
*** yifan <yifan!~yifan@> has joined #yocto14:26
thekappeI can SSH to the board, but I can0t login from the serial terminal14:27
thekappeWhy is that possible?14:27
*** goliath <goliath!> has joined #yocto14:31
erbothekappe: maybe no getty running on the serial console?14:32
thekappeerbo,  don't really know what getty is14:34
thekappebut I was just googling about it14:35
thekappeI expected the service to be there out of the box14:35
erbothekappe: what hw are you building for?14:36
Sponge5FYI fixed my problem: had to rm -rf  workspace/sources/<recipename>, apparently bitbake tried to apply the patch to an already patched file14:36
erboif you know what tty the serial console is on, and you're using systemd, you could just try "systemctl start getty@tty1.service" . Assuming tty1 is the serial console tty.14:37
erboSponge5: when you were done creating the patch, did you use e.g. devtool finish to tell it you were done?14:38
thekappeerbo, /etc/inittab -> 1:12345:respawn:/sbin/getty 38400 tty14:38
Sponge5erbo: yes14:38
thekappemy serial is PS0 @ 11520014:38
Sponge5erbo: but apparently had to delete it too14:39
erboSponge5: weird14:39
Sponge5erbo: wait I didn't use devtool finish, but devtool reset nss14:40
Sponge5erbo: and that wasn't enough14:40
Sponge5didn't know about devtool finish14:40
erbothekappe: so no systemd?14:41
*** kaspter <kaspter!~Instantbi@2409:8a1e:911b:b2b0:ac9b:70b6:b455:2281> has joined #yocto14:42
erbothekappe: I guess you should be able to see in ps output if getty is running14:44
thekappei can see the kernel output14:45
erbonot that getty is running14:45
thekappeand if from ssh i run $ cat "hello" > /dev/ttyPS014:45
thekappeI get Hello from the serial14:45
erboYes, but in order to get a login shell you need something like getty running on that serial14:46
thekappe# ps  | grep getty14:46
thekappe 2123 root      3400 S    /sbin/getty 38400 tty114:46
thekappethat's probably the problem14:46
smurraythekappe: check what the SERIAL_CONSOLES variable is set to, it likely doesn't have an entry for ttyPS014:48
thekappeerbo, changing the line in /etc/inittab fixed the issue14:50
thekappethanks dude14:50
thekappesmurray, I'll check it now14:50
*** B0ned1ger <B0ned1ger!> has quit IRC14:53
*** B0ned1ger <B0ned1ger!> has joined #yocto14:53
*** yifany <yifany!~yifan@> has joined #yocto15:00
*** yifan <yifan!~yifan@> has quit IRC15:00
*** yifany <yifany!~yifan@> has quit IRC15:00
*** sgw1 <sgw1!> has left #yocto15:01
thekappesmurray, SERIAL_CONSOLES does the trick. thanks15:10
smurraythekappe: cool15:10
*** RPI_IMX6 <RPI_IMX6!> has joined #yocto15:11
*** rnouse <rnouse!> has joined #yocto15:11
*** sesom <sesom!> has quit IRC15:17
*** armpit <armpit!~armpit@2601:202:4180:a5c0:2960:99d5:cba5:7114> has quit IRC15:18
*** armpit <armpit!~armpit@2601:202:4180:a5c0:19ce:8609:7a34:860> has joined #yocto15:30
*** B0ned1ger <B0ned1ger!> has quit IRC15:36
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto15:37
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC15:37
*** codysch[m] <codysch[m]!codyschmat@gateway/shell/> has joined #yocto15:41
*** kaspter <kaspter!~Instantbi@2409:8a1e:911b:b2b0:ac9b:70b6:b455:2281> has quit IRC15:55
*** kaspter <kaspter!~Instantbi@2409:8a1e:911b:b2b0:ac9b:70b6:b455:2281> has joined #yocto15:56
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC15:56
*** NiksDev <NiksDev!~NiksDev@> has quit IRC16:02
rburtonpaulbarker: if your ears are burning its because we're talking about and leather on the triage call ;)16:02
rburton'talking about you and leather'16:02
paulbarkermy ears were fine but now I'm worried16:03
rburtonvmeson pointed out that 'barker' historically is a leather tanner16:04
*** kpostlet <kpostlet!~kpostlet@> has quit IRC16:04
paulbarker rburton: I've heard that, as well as that it was the associated with the town crier "barking" out notices16:06
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto16:09
*** sakoman <sakoman!> has quit IRC16:12
*** AndersD_ <AndersD_!> has quit IRC16:13
abelloniah, I forgot the call, I wanted to participate16:13
rburtonabelloni: still on if you want to join the party16:13
abelloniI now realize I never setup notifications...16:13
*** sakoman <sakoman!~steve@> has joined #yocto16:28
*** JaMa <JaMa!> has quit IRC16:31
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC16:33
*** RPI_IMX6 <RPI_IMX6!> has quit IRC16:35
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto16:36
*** yann <yann!~yann@> has quit IRC16:37
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:37
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:38
*** bluelightning_ is now known as bluelightning16:38
*** iamnotyocto <iamnotyocto!59cd8c71@> has joined #yocto16:42
*** sakoman <sakoman!~steve@> has quit IRC16:49
*** vineela <vineela!vtummala@nat/intel/x-okubqtoxdhjfvjaf> has joined #yocto16:49
*** sakoman <sakoman!> has joined #yocto16:50
*** frsc <frsc!> has quit IRC16:50
RPabelloni: Ah, next week for sure then! :)16:50
abellonisure, I managed to join at the end16:51
RPabelloni: I noticed but assumed you were just observing :)16:51
abelloniindeed :)16:52
*** Sponge5 <Sponge5!> has quit IRC16:53
*** rcoote <rcoote!~rcoote@> has joined #yocto16:54
iamnotyoctoSo is there absolutely NO DIFFERENCE whether I use UBUNTU or OPENSUSE?16:59
iamnotyoctofor yocto purposes I mean16:59
iamnotyoctobecause they are both supported17:00
iamnotyoctobut its internals are different17:00
rburtonright, just use the distro you prefer17:02
*** frsc <frsc!> has joined #yocto17:02
*** iamnotyocto <iamnotyocto!59cd8c71@> has quit IRC17:05
*** eduardas <eduardas!> has joined #yocto17:10
*** kaspter <kaspter!~Instantbi@2409:8a1e:911b:b2b0:ac9b:70b6:b455:2281> has quit IRC17:15
*** kaspter <kaspter!~Instantbi@2409:8a1e:911b:b2b0:ac9b:70b6:b455:2281> has joined #yocto17:16
*** iamnotyocto <iamnotyocto!59cd8c71@> has joined #yocto17:31
iamnotyoctorburton cool, thanks17:32
*** kaspter <kaspter!~Instantbi@2409:8a1e:911b:b2b0:ac9b:70b6:b455:2281> has quit IRC17:34
*** mckoan is now known as mckoan|away17:35
*** fl0v0 <fl0v0!~fvo@> has quit IRC17:36
rnouseI have a question regarding delayed postinsts. In OpenBMC we might use e.g. squashfs for rootfs and it always accompanied by RW fs mounted with overlayfs. The question is: what will be a better approach to allow delays postinst? Make it as configurable option (check for another IMAGE_FEATURES that clearly states about overlayfs)?17:42
JPEWrnouse: Do you need to allow them? If so, you could remove the read-only-rootfs IMAGE_FEATURE17:50
*** kiwi_29 <kiwi_29!> has joined #yocto17:51
*** stkw0 <stkw0!> has quit IRC17:51
RPJPEW: I now can't get that reproducer I sent you to work. I am seeing the result of the g++ depend on cwd though :/17:52
JPEWIf you want, you can just send me the two ELF files?17:52
JPEWI had to write our own debug location decoder back when we ran our own RTOS so we could debug our code, so I have a little familiarity with it :)17:53
*** stkw0 <stkw0!> has joined #yocto17:56
RPJPEW: you sound way better placed than me to understand this then. I'll send a couple of binaries over :)17:57
kiwi_29Hello khem  for this repo  there are two bbappend files . Usually a yocto build will have a single version of package and therefore my yocto build errors out complaining there is no version of iptable1.6 available as I only have iptables1.8. . Could you help me understand how do I use your repo and still compile iptables18:06
*** dreyna <dreyna!> has joined #yocto18:06
*** frsc <frsc!> has quit IRC18:12
*** dmoseley <dmoseley!~dmoseley@> has quit IRC18:12
kiwi_29How do I deal with more than one bbappend file in a 3rd party repo. ie more than one bbappend file with diferent versions for same package18:12
khemkiwi_29:  maybe you can BBMASK it if you can not delete it18:13
kiwi_29thanks khem. .. trying now18:15
*** amerigo <amerigo!uid331857@gateway/web/> has quit IRC18:22
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto18:32
*** yizhao <yizhao!~zhaoyi@> has quit IRC18:36
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC18:36
*** dmoseley <dmoseley!~dmoseley@> has quit IRC18:38
*** yizhao <yizhao!~zhaoyi@> has joined #yocto18:39
rnouseJPEW: the rootfs is read-only and removing this image feature might brake other stuff. E.g. read-only-rootfs-hook wouldn't be called. I tho, we just need a way to relax this branch by an option.18:40
kiwi_29khem  putting this. BBMASK += "meta-openwrt/recipe-tweaks/iptables/iptables_1.6%.bbappend"  in build/conf/local.conf does not seem to be working18:41
kiwi_29I am definitely not doing this right. :(18:41
khemmay be try recipe-tweaks/iptables/iptables_1.6%.bbappend18:42
*** dv_ <dv_!~dv@> has quit IRC18:42
khemor just iptables_1.6%.bbappend18:43
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto18:46
kiwi_29thanks khem  just putting iptables_1.6%.bbappend worked !18:47
*** kpo_ <kpo_!> has quit IRC18:47
*** kpo_ <kpo_!> has joined #yocto18:48
*** manuel_ <manuel_!~manuel@> has joined #yocto18:48
*** manuel1985 <manuel1985!~manuel@> has quit IRC18:51
*** dv_ <dv_!~dv@> has joined #yocto18:57
*** manuel_ <manuel_!~manuel@> has quit IRC18:57
JPEWrnouse: I guess it seems a little strange to me to say the rootfs is read-only... but not really19:06
rnouse# mount19:07
rnousedevtmpfs on /dev type devtmpfs (rw,relatime,size=432668k,nr_inodes=108167,mode=755)19:07
rnouseubi0:rwfs on /var type ubifs (rw,relatime,assert=read-only,ubi=0,vol=2)19:07
rnouseoverlay on /etc type overlay (rw,relatime,lowerdir=/etc,upperdir=/var/persist/etc,workdir=/var/persist/etc-work)19:07
rnouseas an example19:07
rnousedev/ubiblock0_1 on / type squashfs (ro,relatime)19:07
JPEWrnouse: Sure, we do something similar, but in our 6 years of doing that, we've never needed a post-install script to run :)19:08
rnousewe need:)19:08
rnousethis is required for migration purpose between root and non-root running processes and files that are already present in read-write back-storage19:09
rnousethe best way is to provide pkg_postinst_ontarget_${PN} routine in per-package recipe that will chown/chmod files upon firstboot after update19:10
rnousethus, we need a relax option for the check above in lib/oe19:10
JPEWRP: I think what's happening is that GCC is changing the order of the items in .debug_loc. I don't know *why*19:18
JPEWRP: Where did ParseHelper.cpp come from ?19:19
JPEWI could not find it in the Vulkan-Samples repo19:19
*** mbulut <mbulut!> has joined #yocto19:20
JPEWRP: Ah in a submodule...19:28
*** aidanh_ <aidanh_!~aidanh@unaffiliated/aidanh> has joined #yocto19:38
*** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has quit IRC19:39
*** aidanh_ is now known as aidanh19:39
*** sakoman <sakoman!> has quit IRC19:41
*** sakoman <sakoman!> has joined #yocto19:45
*** minimaxwell <minimaxwell!> has quit IRC19:47
*** eduardas <eduardas!> has quit IRC19:48
*** Bunio_FH <Bunio_FH!> has quit IRC19:57
*** sakoman <sakoman!> has quit IRC20:00
*** iamnotyocto <iamnotyocto!59cd8c71@> has quit IRC20:02
*** rcoote <rcoote!~rcoote@> has quit IRC20:03
rnouseJPEW any thoughts on relaxing option?20:04
*** Bunio_FH <Bunio_FH!> has joined #yocto20:12
*** sakoman <sakoman!~steve@> has joined #yocto20:16
*** imaami <imaami!> has joined #yocto20:16
imaamiDoes bitbake have a formal syntax definition for its config files, and why not?20:17
JPEWrnouse: It still doesn't quite make sense to me... I don't think you want *all* post-install scripts to run, some of them will surely fail because not all of your rootfs is RW20:25
*** sgw <sgw!> has joined #yocto20:35
rnouseThose post-install scripts are run during rootfs population, but the mentioned delays postinstall (pkg_postinst_ontarget_${PN}) present only in a few recipes:
*** B0ned1ger2 <B0ned1ger2!> has quit IRC20:36
*** B0ned1ger <B0ned1ger!> has joined #yocto20:37
JPEWimaami: Like a grammar definition?20:46
JPEWrnouse: Sure.... I guess I'm still skeptical. It seems highly specific to your setup as to whether those can actually run or not20:48
JPEWI guess maybe you can have some knob that you set that bascially says "I acknowledge this will only work if I validate all the pkg_postinst_ontarget for all the packages I'm installing only write to places I've marked RW"20:49
RPJPEW: if it were just order the size of the section wouldn't change?20:50
JPEWRP... Hmm. maybe. It's using some new-fangled GNU locview format I've never seen before20:51
JPEWDWARF does a lot of compression tricks, so it would not suprise me if an order change changed the size, but it could be something else also20:51
JPEWOr perhaps, the content changed, which caused the order to change20:51
RPJPEW: right, I'm out my depth :/20:52
*** jobroe <jobroe!> has quit IRC20:52
JPEWRP: Ya. Unfortunately, I'm having trouble finding the locview extension documentation20:56
*** Konsgn <Konsgn!~Konsgnx3@unafiliated/joyseph> has quit IRC20:56
JPEWDWARF is really well documented... the GNU extensions no so much20:57
*** mbulut <mbulut!> has quit IRC20:57
*** medo <medo!d1851b4a@> has joined #yocto21:06
medoHi, for somethign like the iptables recipe what do the .rules file type mean? Is this a yocto thing or a linux thing ?21:07
rnouseJPEW: > I acknowledge this will only21:08
rnouseyeah, that's an original idea -- set the relaxing flag to bypass this check21:08
medoI see that the do_isntall uses those rules but how do you configure them for your specific image ?21:08
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/> has quit IRC21:16
*** kiwi_29 <kiwi_29!> has quit IRC21:26
*** alephan <alephan!andreicubi@gateway/shell/> has quit IRC21:30
*** paulbarker_tmp <paulbarker_tmp!pbarkermat@gateway/shell/> has quit IRC21:30
*** rsalveti <rsalveti!uid117878@gateway/web/> has quit IRC21:30
*** paulbarker_tmp <paulbarker_tmp!pbarkermat@gateway/shell/> has joined #yocto21:30
*** alephan <alephan!andreicubi@gateway/shell/> has joined #yocto21:31
*** rsalveti <rsalveti!uid117878@gateway/web/> has joined #yocto21:33
RPJPEW: any idea why the debug_str section would have the cwd at compile time embedded in it?21:43
RPJPEW: I simplified the test case down to a nearly empty file and am seeing that, seems a bit odd21:43
JPEWRP: No I don't21:45
JPEWRP: I didn't see that in the file you gave me21:46
JPEWUnless it's the "1/4 stride is too large"21:47
RPJPEW: no, I tried to trim the example down to bare bones and I see this21:47
RPJPEW: I'm seeing this even with my host g++ :/21:50
JPEWEven with the debug prefix mapping option passed to g++?21:51
*** leon-anavi <leon-anavi!~Leon@> has quit IRC21:56
RPJPEW: I've messaged you the weirdness. I must be missing something obvious but the binary output depends on cwd :/21:57
RPJPEW: I suspect in a larger more complex program the same issue could get abstracted away into debug_loc weirdness? particularly if the prefix was already remapped away by the prefix mapping22:07
RPI also suspect ninja isn't particular about its cwds22:07
*** JPEW_ <JPEW_!~JPEW@2605:a601:ac3d:c100:4f37:550:d1b1:6f01> has joined #yocto22:11
JPEW_Hmm, DW_AT_comp_dir seems suspect22:12
RPJPEW: ah, yes. Also - wonder if that was merged22:16
JPEW_RP: Yep! that would do it22:16
JPEW_I think the confusing thing with your example is that it outputs the string even when there is no debug data referencing it22:17
RPJPEW: right, but doesn't that patch imply it would do that?22:17
JPEW_If you add a trivial function to the source instead of an empty file, it show up in the debug info pretty clearly22:17
RPJPEW: confirmed that code is in gcc so it will always generate it. I'm not sure if it should be optimised out or not22:19
JPEW_It respectes -fdebug-prefix-map if that helps22:21
rnouseJPEW, so, what about relaxing option?22:21
RPJPEW: definitely does, just means we'd need to teach vulkan about keeping cwd sane22:21
RPJPEW: -feliminate-unused-debug-types -feliminate-unused-debug-symbols didn't help22:22
JPEW_RP: Hmm, I don't really see what vulkan is doing that is so different... but I haven't looked *too* close22:26
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC22:28
RPJPEW: right, it is setting a consistent directory by the looks of it so I think I've just veered into a quagmire trying to simplify the testcase22:30
RPJPEW: sorry, it did look like a promising lead22:30
*** B0ned1ger <B0ned1ger!> has quit IRC22:37
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto22:37
*** risca <risca!~quassel@> has quit IRC23:06
*** risca <risca!~quassel@> has joined #yocto23:07
*** kpo_ <kpo_!> has quit IRC23:17
*** kpo_ <kpo_!> has joined #yocto23:18
*** beneth <beneth!> has left #yocto23:31
*** medo <medo!d1851b4a@> has quit IRC23:38
idadelHello everyone, please I need some help. I started running a build using the poky-contrib repo and  specifically paule/rpurdie-license-experiments-osls branch. I had some errors at first but after rebasing on top of master my build was up and running well until this other error showed up. Here's the error I got.23:44

Generated by 2.17.2 by Marius Gedminas - find it at!