Wednesday, 2021-03-17

*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC00:02
*** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has joined #yocto00:15
*** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has quit IRC00:20
*** stephano <stephano!~stephano@73.240.0.134> has quit IRC00:35
*** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has quit IRC00:37
*** dev1990 <dev1990!~dev@dynamic-78-8-240-165.ssp.dialog.net.pl> has quit IRC00:41
*** kaspter <kaspter!~Instantbi@119.137.52.131> has joined #yocto01:05
*** camus <camus!~Instantbi@218.17.39.2> has joined #yocto01:08
*** kaspter <kaspter!~Instantbi@119.137.52.131> has quit IRC01:09
*** camus is now known as kaspter01:09
*** yann <yann!~yann@88.120.44.86> has quit IRC01:13
armpitalephan, I have that sitting in dunfell-next. I just need to ask for a merge01:21
alephanGreat. Thanks!01:22
*** Kyubi <Kyubi!~Kyubi@2601:647:4080:f10:9176:f441:b06b:5cf> has joined #yocto01:40
*** kaspter <kaspter!~Instantbi@218.17.39.2> has quit IRC01:41
*** Kyubi <Kyubi!~Kyubi@2601:647:4080:f10:9176:f441:b06b:5cf> has quit IRC01:55
*** kaspter <kaspter!~Instantbi@183.15.179.234> has joined #yocto02:19
*** Kyubi <Kyubi!~Kyubi@149.199.62.130> has joined #yocto02:29
*** camus <camus!~Instantbi@183.15.178.130> has joined #yocto02:35
*** kaspter <kaspter!~Instantbi@183.15.179.234> has quit IRC02:37
*** camus is now known as kaspter02:37
*** tedfernau <tedfernau!~tedfernau@c-76-104-226-12.hsd1.wa.comcast.net> has quit IRC02:38
*** sakoman <sakoman!~steve@72.173.249.164> has quit IRC02:42
*** sakoman <sakoman!~steve@72.173.249.164> has joined #yocto02:56
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-bizdxvsthtvcxqyi> has quit IRC03:04
*** sakoman <sakoman!~steve@72.173.249.164> has quit IRC03:11
*** paulbarker <paulbarker!sid269702@gateway/web/irccloud.com/x-enhyxqmlgvtymjaw> has joined #yocto03:29
*** SWAT <SWAT!~swat@ubuntu/member/swat> has quit IRC03:37
*** SWAT <SWAT!~swat@ubuntu/member/swat> has joined #yocto03:40
*** oberstet <oberstet!~oberstet@213.170.219.39> has quit IRC03:44
*** vineela <vineela!vtummala@nat/intel/x-pasuelmhusbjxmzt> has quit IRC03:48
*** ahadi <ahadi!~ahadi@88.130.219.166> has quit IRC03:55
*** ahadi_ <ahadi_!~ahadi@89.244.121.238> has joined #yocto03:56
*** armpit <armpit!~armpit@2601:202:4180:a5c0:f56b:e4ef:635c:c0de> has quit IRC04:15
*** [Sno] <[Sno]!~sno@xdsl-81-173-140-163.nc.de> has joined #yocto04:21
*** sno <sno!~sno@xdsl-89-0-223-73.nc.de> has quit IRC04:24
*** armpit <armpit!~armpit@2601:202:4180:a5c0:25c8:44cd:2453:cf2a> has joined #yocto04:27
*** itseris <itseris!~itseris@d23-16-24-169.bchsia.telus.net> has quit IRC04:41
*** vineela <vineela!~vtummala@134.134.137.77> has joined #yocto04:55
*** vineela <vineela!~vtummala@134.134.137.77> has quit IRC05:00
*** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has joined #yocto05:42
*** jobroe <jobroe!~manjaro-u@p579eb888.dip0.t-ipconnect.de> has joined #yocto05:47
*** SWAT <SWAT!~swat@ubuntu/member/swat> has quit IRC06:09
*** SWAT <SWAT!~swat@ubuntu/member/swat> has joined #yocto06:11
*** tlwoerner <tlwoerner!~tlwoerner@unaffiliated/tlwoerner> has quit IRC06:18
*** tlwoerner_ <tlwoerner_!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has joined #yocto06:18
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has joined #yocto06:24
*** AndersD_ <AndersD_!~AndersD@h-17-226.A137.corp.bahnhof.se> has joined #yocto06:27
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:44dc:84ad:f7d8:ff52> has joined #yocto06:28
*** AndersD <AndersD!~AndersD@h83-209-96-136.cust.a3fiber.se> has quit IRC06:30
*** ENPJ <ENPJ!~ENPJ@2001:a61:3a33:7901:a9f0:885a:b6b3:4a54> has joined #yocto06:33
*** B0ned1ger <B0ned1ger!~B0ned1ger@82-135-139-249.static.zebra.lt> has joined #yocto06:34
*** Spooster <Spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has quit IRC06:40
*** Spooster <Spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has joined #yocto06:41
*** Spooster <Spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has quit IRC06:45
*** agust <agust!~agust@p508b6964.dip0.t-ipconnect.de> has joined #yocto06:47
*** pcglue <pcglue!~kvirc@cpe-104-175-108-43.socal.res.rr.com> has joined #yocto06:48
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto06:51
*** simonpe^^ <simonpe^^!~starlord@c83-252-164-58.bredband.comhem.se> has joined #yocto07:02
*** ThomasD13 <ThomasD13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto07:07
*** ENPJ <ENPJ!~ENPJ@2001:a61:3a33:7901:a9f0:885a:b6b3:4a54> has quit IRC07:12
*** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has quit IRC07:15
*** mihai-- is now known as mihai07:30
*** frsc <frsc!~frsc@i59F72043.versanet.de> has joined #yocto07:36
*** mckoan|away <mckoan|away!~marco@unaffiliated/mckoan> has quit IRC07:46
*** kaspter <kaspter!~Instantbi@183.15.178.130> has quit IRC07:49
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has joined #yocto07:50
*** matteo <matteo!~matteo@redhat/matteo> has joined #yocto07:51
*** mckoan_ <mckoan_!~marco@unaffiliated/mckoan> has joined #yocto07:53
mckoan_good morning07:53
simonpe^^Hi! I have a kernel and bootloader combo from some old NXP crapper that boots, for reasons not related to this question I've ripped out u-boot, arm-trusted-firmware, and imx-firmware from bitbake and build it on the side, flash it to the mmc of my imx8mn-ddr4-evk board and try to boot a fit image with the same kernel and dtb as before. Thing is, I'm getting a kernel panic when booting and I'm not really07:53
simonpe^^sure what went wrong. I'd appreciate very much if someone could have a look at it. https://pastebin.com/mQ6m1fWq07:53
*** mckoan_ is now known as mckoan|away07:54
*** fl0v0 <fl0v0!~fvo@i5E86AD7E.versanet.de> has joined #yocto07:54
*** mckoan|away <mckoan|away!~marco@unaffiliated/mckoan> has quit IRC07:54
*** mckoan_ <mckoan_!~marco@unaffiliated/mckoan> has joined #yocto07:54
simonpe^^I'm not expecting someone to solve my problem but I'm pretty much stuck on this for several days so just asking some relevant questions might lead me on the right path07:55
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto08:02
*** caiortp <caiortp!~caiortp@92-108-245-63.cable.dynamic.v4.ziggo.nl> has joined #yocto08:05
*** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:a837:43a1:f9fb:9eec> has joined #yocto08:06
*** sstiller <sstiller!~sstiller@p200300f07f121d00044444c1f74b03fb.dip0.t-ipconnect.de> has joined #yocto08:07
*** pcglue <pcglue!~kvirc@cpe-104-175-108-43.socal.res.rr.com> has quit IRC08:10
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has joined #yocto08:10
*** MartinH97 <MartinH97!2edfa3d6@HSI-KBW-46-223-163-214.hsi.kabel-badenwuerttemberg.de> has joined #yocto08:25
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has joined #yocto08:27
MartinH97Hello community, I have some trouble with a self written external kernel module, very close to the hello_mod example. My module also provides a public header file to be provided to all code using the module. Can someone help me with the correct way to install this header? Do I modify my kernel module makefile or do I deploy the header with08:28
MartinH97do_install_append from the recipe? Thanks!08:28
*** caiortp <caiortp!~caiortp@92-108-245-63.cable.dynamic.v4.ziggo.nl> has quit IRC08:29
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/irccloud.com/x-rwztvrrdsnxovcja> has joined #yocto08:29
LetoThe2ndyo dudX08:33
qschulzo/08:33
mckoan_hello :-)08:34
LetoThe2ndqschulz: \o08:34
mckoan_khem: ping08:35
*** yann <yann!~yann@88.120.44.86> has joined #yocto08:36
qschulzMartinH97: if you need to share a header during compilation time, you should install the file in a directory listed in SYSROOT_DIRS (${include} is :) ) if you need it at runtime, you need to install in a directory that is included in a package that you ask Yocto to install in the image (IMAGE_INSTALL usually)08:36
qschulzto define which directory is installed in which package, have a look at FILES_${PN}* variables08:37
*** grma <grma!~gruberm@80.93.38.128> has quit IRC08:38
*** dreyna_ <dreyna_!~dreyna@c-71-202-37-249.hsd1.ca.comcast.net> has quit IRC08:39
MartinH97qschulz thanks! When I add the following to modules_install in the module Makefile I get an error /usr/share/include no access rights: "install -m 644 -D header.h $(DESTDIR)$(includedir)/header.h"08:41
MartinH97When I try to do this via do_install_append() I get the error: run.do_install.4165502: 111: includedir: not found08:42
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has quit IRC08:44
qschulzMartinH97: in recipes, it's curly-brackets, not parenthesis around variables, i.e. ${D}${includedir} is where you should install your header08:49
qschulzMartinH97: includedir in your Makefile looks wrong, seems DESTDIR is also not set correctly08:50
*** ENPJ <ENPJ!~ENPJ@2001:a61:24aa:d201:a9f0:885a:b6b3:4a54> has joined #yocto08:50
qschulzMartinH97: or let's say, not wrong but different from the includedir from Yocto PoV (/usr/include)08:51
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has joined #yocto08:52
MartinH97qschulz what is the right way to install a header of a kernel module from its makefile (ignoring all Yocto for the moment)08:53
qschulzMartinH97: I should have started with this question: what exactly do you want to do? What's the use case for this header file? Why does it exist :)08:53
GeneralStupidHi, how should i normally manipulate config files? I need to reconfigure systemd-journal.08:55
MartinH97qschulz good point;-)  I want to compile and install an external kernel module including its header file. The header file shall be available to other recipes and to SDK. My current kernel module makefile does not yet install the header.08:55
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC08:56
*** codetronaut[m] <codetronaut[m]!anmolkmatr@gateway/shell/matrix.org/x-oevefrbulpxhlffu> has quit IRC09:00
GeneralStupidI tried a bbappend and installed my own config file. But this does not work, its still the original conf file09:00
*** tnovotny <tnovotny!~tnovotny@ip-78-45-64-220.net.upcbroadband.cz> has joined #yocto09:00
LetoThe2ndGeneralStupid: an append with prepending the file path is the usual way. if it is not being picked up, you might need to dig deeper (and check that the file actually is being puled in from somewhere, instead of being created)09:07
GeneralStupidLetoThe2nd: Ok, so i have to take a deeper look. Thank you09:08
LetoThe2ndGeneralStupid: have fun!09:09
qschulzGeneralStupid: also triple check it's really FILESEXTRAPATHS_prepend := in your bbappend, it's common to have typos :)09:12
qschulzMartinH97: What I would recommend is to have a simple recipe which only give the header file. Then this "header" recipe would be added to your module recipe via DEPENDS, and you could install it in your SDK too09:13
qschulzMartinH97: the split from your kernel module recipe is not per-se required but it probably makes more sense from a logical standpoint09:14
qschulzMartinH97: basically, what I'm going for right now, is that installing the kernel header file from your kernel module from its Makefile seems wrong, because that's very unusual (modules_install installs the .ko and depmod and all, but no header file since it's not needed on the system)09:15
MartinH97qschulz: interesting suggestion! I was drifting of into researching how to support "make headers_install" from my modules Makefile, but didn't find a clean solution yet.09:16
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has quit IRC09:17
*** kaspter <kaspter!~Instantbi@119.137.55.62> has joined #yocto09:26
*** psnsilva_ <psnsilva_!~psnsilva@161.230.35.203> has joined #yocto09:33
*** prabhakarlad <prabhakarlad!51988ebd@host81-152-142-189.range81-152.btcentralplus.com> has joined #yocto09:36
MartinH97qschulz: thanks for the input! a simple do_install_append() fixed the issue so that the header file is now included to sysroot and SDK. Sometimes a second pair of eyes is very helpful!09:38
qschulzMartinH97: that's what we're here for, happy that we could help you :)09:40
MartinH97Other question O:3  what is the correct way to add kernel headers (headers only!) to the SDK. There is a lot of chatter on the mailinglist documented, like kernel-devsrc, but what is the current up to date solution?09:41
*** tlwoerner_ <tlwoerner_!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has quit IRC09:45
*** tnovotny_ <tnovotny_!~tnovotny@ip-78-45-64-220.net.upcbroadband.cz> has joined #yocto09:46
*** tlwoerner_ <tlwoerner_!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has joined #yocto09:46
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto09:48
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has joined #yocto09:49
*** simonpe^1 <simonpe^1!~starlord@c83-252-164-58.bredband.comhem.se> has joined #yocto09:50
*** mbulut <mbulut!~nameclash@ip1f121f26.dynamic.kabel-deutschland.de> has quit IRC09:51
*** tnovotny <tnovotny!~tnovotny@ip-78-45-64-220.net.upcbroadband.cz> has quit IRC09:55
*** simonpe^^ <simonpe^^!~starlord@c83-252-164-58.bredband.comhem.se> has quit IRC09:55
*** agust <agust!~agust@p508b6964.dip0.t-ipconnect.de> has quit IRC09:55
*** blueness_ <blueness_!~blueness@cpe-172-100-14-17.twcny.res.rr.com> has quit IRC09:55
*** psnsilva_ <psnsilva_!~psnsilva@161.230.35.203> has quit IRC09:57
*** psnsilva <psnsilva!~psnsilva@161.230.35.203> has joined #yocto09:58
*** psnsilva_ <psnsilva_!~psnsilva@161.230.35.203> has joined #yocto09:58
LetoThe2ndqschulz: speak for yourself. i'm not happy.09:58
*** kaspter <kaspter!~Instantbi@119.137.55.62> has quit IRC10:04
qschulzLetoThe2nd: sorry you feel this way, you'll have better days. /me offers a virtual hug10:06
LetoThe2ndcan't you offer a fix why kas-docker in lxc b0rks here? ;-)10:07
*** ebail <ebail!~ebail@alille-157-1-119-102.w92-131.abo.wanadoo.fr> has joined #yocto10:08
ebailHi guys, I want to archive some artifacts with a custom .bbclass started once the build of my image is done. I am trying to retrieve the path of .config file of PREFERRED_PROVIDER_virtual/kernel.10:09
qschulzLetoThe2nd: I prefer to send a virtual beer to help you cope, can't offer better :/10:10
LetoThe2ndebail: apply yocto chant #1:)10:10
LetoThe2ndqschulz: hrhr10:10
ebail:)10:11
ebailI am looking on STAGING_KERNEL_DIR varialbe but it is not pointing to my Kernel build dir10:11
qschulzebail: recipe data is local, you cna't access it from your image recipe since the image recipe is in fact... a recipe10:12
*** Fanfwe is now known as wb10:13
ebailyes qschulz that is the reason of my question.10:13
qschulzebail: the possible way to do that would be to create (or append to) deploy tasks in recipes you want artifacts from10:13
ebailqschulz: I am using a bbclass so I might add a task10:14
qschulzand from your image recipe, get the files from the DEPLOY_DIR_IMAGE10:14
*** [Sno] <[Sno]!~sno@xdsl-81-173-140-163.nc.de> has quit IRC10:14
LetoThe2ndebail: if the class is inherited in the image, #1 still applies nonetheless.10:14
qschulzebail: the class will need to be added to each recipe you want artifact from, not sure a class would scale actually, might be better off with bbappends10:14
kmaincentRP: abelloni asked me to take a look at bug 14268. Have you an idea of when it happened, to find the swatbot log?10:15
LetoThe2ndif at all then you need two classes. one exporting the data as qschulz said, being added to all kernel providers, and another one picking everything up, added to all images :)10:15
ebailqschulz: Note: I don't need to embed the artifacts (ex: .config) in my image.10:16
ebailyes LetoThe2nd I have no choice to export my.config in my Kernel recipe10:16
ebailwill do that ;)10:17
LetoThe2ndebail: have fun10:17
ebailThanks. And cheers / prost / santé ;)10:18
LetoThe2ndi'm not as think as you drunk i am! ;-)10:18
qschulzam neither I10:19
*** wb is now known as Fanfwe10:20
*** ENPJ <ENPJ!~ENPJ@2001:a61:24aa:d201:a9f0:885a:b6b3:4a54> has quit IRC10:25
*** Saur4 <Saur4!5e89711f@94-137-113-31.customers.ownit.se> has joined #yocto10:26
*** Saur4 is now known as Saur|Home10:27
*** ENPJ <ENPJ!~ENPJ@2001:a61:24aa:d201:a9f0:885a:b6b3:4a54> has joined #yocto10:27
*** cengiz_io_ <cengiz_io_!~cengiz_io@159.89.7.238> has quit IRC10:29
*** cengiz_io <cengiz_io!~cengiz_io@159.89.7.238> has joined #yocto10:29
Saur|HomeRP: I'm getting errors due to "do_package in both covered and notcovered." I first saw it when building with our layers included and thought it was something we were doing, but today I got it when building with only layers from OE-Core and OE. I seem to get it for some random set of recipes (at least there is nothing obvious about the recipes that10:32
Saur|Homegave the errors).10:32
*** B0ned1ger <B0ned1ger!~B0ned1ger@82-135-139-249.static.zebra.lt> has quit IRC10:34
*** B0ned1ger <B0ned1ger!~B0ned1ger@82-135-139-249.static.zebra.lt> has joined #yocto10:34
*** rhadye <rhadye!sid217449@gateway/web/irccloud.com/x-rmyrccxdawjijmaw> has quit IRC10:35
*** rhadye <rhadye!sid217449@gateway/web/irccloud.com/x-rshwgiphrhadvjli> has joined #yocto10:35
*** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has quit IRC10:36
RPSaur|Home: that sanity check was added recently and means bad thing are going on :(10:41
Saur|HomeYeah, I know. The problem is that I don't know what those bad things are and what to look for...10:41
RPSaur|Home: I don't really know what to advise. The output from -DD is helpful and looking at the messages around the point this task is added to "covered" and "uncovered". Obviously one of the additions isn't right, question is which bit of the code it is hitting10:43
RPSaur|Home: if you can reproduce it with a -DD log, I'm happy to take a look10:43
*** dev1990 <dev1990!~dev@dynamic-78-8-240-165.ssp.dialog.net.pl> has joined #yocto10:44
RPSaur|Home: was pseudo-native unavailable and the hard dependency code kicked in?10:46
RPThe mention of do_package makes me suspect that10:46
Saur|HomeRP: It seems to have built pseudo-native in the build that had errors, if that was what you meant?10:49
Saur|HomeBasically, what I did was to update poky and meta-openembedded to latest and rebuilt. Last time I had done that was a week ago.10:51
RPSaur|Home: did it skip setscene for the covered/uncovered tasks due to pseudo-native being missing?10:53
Saur|HomeHow can I tell?10:53
RPSaur|Home: the logs, not sure if the log level would be high enough or not10:54
RPSaur|Home: A while ago I was basically overruled about whether we should have noisy useful logs so we do on the autobuilder, we don't elsewhere :(10:54
Saur|HomeRP: Well, I would love more logging in the tmp/log/cooker/ files as long as I don't get all that in the terminal while running bitbake. Would that be possible?10:57
*** grma <grma!~gruberm@80.93.38.128> has joined #yocto10:59
*** medaliyou <medaliyou!c4b3dd32@196.179.221.50> has joined #yocto10:59
*** tnovotny_ <tnovotny_!~tnovotny@ip-78-45-64-220.net.upcbroadband.cz> has quit IRC11:00
medaliyouHi, how to tell bitbake to use specific u-boot version (or maybe a branch or commit) ?11:00
LetoThe2ndmedaliyou: by providing a recipe for it. if you have multiple recipes, PREFERRED_VERSION and PREFERRED_PROVIDER can be used to select.11:02
LetoThe2ndmedaliyou: and no, you can#t just set UBOOT_VERSION_I_WANT = "xxx.yy" somewhere. it doesn't work like that.11:02
*** zkrx <zkrx!~slimshady@adsl-89-217-237-59.adslplus.ch> has joined #yocto11:05
RPSaur|Home: anything is possible. With the current codebase it isn't practical11:08
Saur|HomeRP: Too bad. It would have been useful to be able to get the full log after a failed build, without having to watch them when building normally.11:09
RPSaur|Home: its something I'd like to change/fix11:10
RPSaur|Home: one challenge is that in most automated builder environments it is the console output which ends up easiest to save11:11
RPbut we already know how to adjust that11:11
Saur|HomeRP: Another thing: the "SOURCE_DATE_EPOCH value from sstate '0' is deprecated/invalid." warning. Is it really useful for anything? It doesn't give any useful information, e.g., what recipe or file was at fault. So based on the warning, there is nothing I can do to avoid it.11:11
RPSaur|Home: that should disappear over time and is mainly a sign that your environment hasn't quite moved forward yet11:16
RPSaur|Home: if that doesn't disappear, we have a problem11:16
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has joined #yocto11:17
RPSaur|Home: the fact it isn't easily traced is a different problem, it is warning of something which should not happen11:17
Saur|HomeI know it should, but since I cannot do anything to prevent the warning, it doesn't seem useful. To me it is just noise.11:17
*** yizhao <yizhao!~zhaoyi@60.247.85.82> has quit IRC11:18
RPSaur|Home: you could debug it and find out why it is happening?11:18
Saur|HomeHow?11:18
RPHaving signs that something is wrong is probably better than having no evidence at all and things just silently breaking11:19
*** yizhao <yizhao!~zhaoyi@60.247.85.82> has joined #yocto11:19
RPwell, figure out which task it is coming from? I'm not seeing the warning here and I don't know of any system which is. I'd have thought it'd be in some task logs files somewhere so grep for it maybe?11:20
RPmaybe improve the warning message so it can be traced?11:20
RPThe fact it doesn't have a task prefix is a little strange in itself as task based log messages should have11:21
RPbut I am pretty blind here as I don't know what you're seeing other that what you've pasted above which could mean several things :(11:21
medaliyouLetoThe2nd Can i do it from a bbappend in a custom meta layer ?11:22
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC11:23
Saur|HomeWell, all I get is "WARNING: SOURCE_DATE_EPOCH value from sstate '0' is deprecated/invalid. Reverting to SOURCE_DATE_EPOCH_FALLBACK '1302044400'" so there is not much to go on. It is very possible that it, as you say, is just something that will go away over time. E.g., I have not built in this particular build tree for over a week, and not much11:24
Saur|Homebefore that either.11:24
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto11:24
RPSaur|Home: if it was an existing build then it is possible things aren't cleanly updating, I really don't know11:25
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto11:26
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:44dc:84ad:f7d8:ff52> has quit IRC11:36
*** berton <berton!~user@200-180-244-11.user3p.brasiltelecom.net.br> has joined #yocto11:36
*** mckoan_ is now known as mckoan|away11:40
*** yizhao <yizhao!~zhaoyi@60.247.85.82> has quit IRC11:41
*** yizhao <yizhao!~zhaoyi@60.247.85.82> has joined #yocto11:44
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has quit IRC11:48
*** caiortp <caiortp!~caiortp@92-108-245-63.cable.dynamic.v4.ziggo.nl> has joined #yocto11:56
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has joined #yocto12:01
*** psnsilva_ <psnsilva_!~psnsilva@161.230.35.203> has quit IRC12:03
*** psnsilva <psnsilva!~psnsilva@161.230.35.203> has quit IRC12:03
*** psnsilva <psnsilva!~psnsilva@161.230.35.203> has joined #yocto12:04
*** simonpe^1 <simonpe^1!~starlord@c83-252-164-58.bredband.comhem.se> has quit IRC12:12
*** dleppich <dleppich!~Thunderbi@p5098be52.dip0.t-ipconnect.de> has joined #yocto12:21
*** dleppich <dleppich!~Thunderbi@p5098be52.dip0.t-ipconnect.de> has quit IRC12:22
*** tnovotny <tnovotny!~tnovotny@ip-78-45-64-220.net.upcbroadband.cz> has joined #yocto12:22
*** tlwoerner_ <tlwoerner_!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has quit IRC12:27
*** tlwoerner <tlwoerner!~tlwoerner@unaffiliated/tlwoerner> has joined #yocto12:28
*** simonpe^^ <simonpe^^!~starlord@c83-252-164-58.bredband.comhem.se> has joined #yocto12:39
*** kpo_ <kpo_!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC12:46
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto12:46
*** Spooster <Spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has joined #yocto12:51
*** Spooster <Spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has quit IRC12:52
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has quit IRC12:53
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-idcoblthgaikdjcw> has joined #yocto12:55
*** Spooster <Spooster!~Spooster@c-68-61-72-182.hsd1.mi.comcast.net> has joined #yocto12:59
*** yates <yates!~user@fv-nc-f7af8b91e1-234237-1.tingfiber.com> has quit IRC13:15
*** agust <agust!~agust@p508b6964.dip0.t-ipconnect.de> has joined #yocto13:17
*** yates <yates!~user@fv-nc-f7af8b91e1-234237-1.tingfiber.com> has joined #yocto13:23
*** lexano <lexano!~lexano@cpeb03956d8c2f4-cm98524a70e35e.cpe.net.cable.rogers.com> has quit IRC13:23
yatesis it not true that, to do just about anything, yocto/poky has to build or some obtain cross-tools (assembler, linker, compiler, etc.) for the target architecture?13:25
yatesif so, then which recipe is responsible for this?13:26
*** lexano <lexano!~lexano@cpeb03956d8c2f4-cm98524a70e35e.cpe.net.cable.rogers.com> has joined #yocto13:26
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has joined #yocto13:28
*** medaliyou <medaliyou!c4b3dd32@196.179.221.50> has quit IRC13:29
yatesis there a way i can find out for myself? i.e., is there a way to cause bitbake to emit an ordered (prioritized) list the recipes/tasks it has built in its task queue?13:29
yatesi am working with a new machine architecture which has never been built under yocto, that i can tell, and as i see it this must be the first step13:32
LetoThe2ndyates: have a good look at recipes-core and recipes-devtools. and for example at meta-risc, as thats essentially what it does: inject a completely new ISA.13:34
yatesok thanks LetoThe2nd13:34
*** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:a837:43a1:f9fb:9eec> has quit IRC13:37
*** Yumasi <Yumasi!~guillaume@40.72.95.92.rev.sfr.net> has joined #yocto13:39
yatesLetoThe2nd: i cannot find meta-risc. where are you seeing this?13:39
yatesdid you mean meta-riscv?13:40
LetoThe2ndyates: yeah.13:40
yatesis "inherit" == "INHERIT"?13:56
* RP notes his plan to remove stale sstate has flaws :(13:56
yatesRP: dental flaws?13:57
*** sakoman <sakoman!~steve@72.173.249.164> has joined #yocto14:00
*** kaspter <kaspter!~Instantbi@119.137.54.203> has joined #yocto14:01
*** bonettor <bonettor!5e2479d3@94-36-121-211.adsl-ull.clienti.tiscali.it> has joined #yocto14:02
RPyates: no, thankfully not :)14:03
qschulzyates: INHERIT is inherit applied to all recipes14:11
qschulzIIRC14:11
yatesLetoThe2nd: drilling down a bit, it appears the main workhorse is the cross-canadian.bbclass class. it looks like it's responsible for AR, AS, GCC, etc. am i on the right track?14:13
*** kaspter <kaspter!~Instantbi@119.137.54.203> has quit IRC14:13
*** kaspter <kaspter!~Instantbi@119.137.54.203> has joined #yocto14:14
LetoThe2ndyates: anything cross canadian sounds like a good start, yes.14:17
GeneralStupidI just found out that, if you want to change systemd configuration you need to append to systemd-conf.bb not systemd.bb.14:17
*** ncaidin_lf <ncaidin_lf!a2fa0254@162.250.2.84> has joined #yocto14:18
*** jUnG3 <jUnG3!3e6041d4@62.96.65.212> has joined #yocto14:19
*** ssajal <ssajal!~ssajal@bras-base-otwaon1146w-grc-06-184-146-108-8.dsl.bell.ca> has joined #yocto14:20
vdlcan we add a txt file from the image recipe? like cat >> ${IMAGE_ROOTFS}/foo?14:41
qschulzvdl: in the correct tasks yes14:41
RPvdl: look at the rootfs-postcommands.bbclass iirc14:42
*** Blackbetty <Blackbetty!540affd6@84-10-255-214.static.chello.pl> has joined #yocto14:43
sgwabelloni: RP: just trying to do some swat this morning, is "AUH" builds part of swat?14:43
RPsgw: no14:43
BlackbettyHello!14:45
BlackbettyIm kinda stuck. My yocto builds wrong libunwind recipe (from layer meta), when i want to build from (meta-qti-bsp).14:45
Blackbetty`bitbake-layers show-layers` shows priorities:14:45
Blackbettymeta-qti-bsp <path> 1714:45
Blackbettymeta <path> 514:45
Blackbettyany ideas what else may be wrong?14:45
*** camus <camus!~Instantbi@119.137.54.185> has joined #yocto14:45
*** kaspter <kaspter!~Instantbi@119.137.54.203> has quit IRC14:45
*** camus is now known as kaspter14:46
*** stephano <stephano!~stephano@73.240.0.134> has joined #yocto14:55
qschulzBlackbetty: look for PREFERRED_VERSION_libunwind variable, maybe it's set?14:55
sgwRP: looks like the other failure seems to be a cascaded failure from a filesystem issue (read-only)14:55
*** Firuxabade <Firuxabade!~firuxabad@2001:e68:544d:e93c:5866:a7c5:cb56:f81> has quit IRC14:58
RPsgw: yes, sounds likely. I think that worker was paused and repaired15:03
*** jobroe <jobroe!~manjaro-u@p579eb888.dip0.t-ipconnect.de> has quit IRC15:04
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has quit IRC15:05
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:44dc:84ad:f7d8:ff52> has joined #yocto15:06
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC15:11
*** simonpe^^ <simonpe^^!~starlord@c83-252-164-58.bredband.comhem.se> has quit IRC15:22
JaMaBlackbetty: or the one from meta provides something which the version from meta-qti-bsp doesn't and something depend on this, I usually add PNBLACKLIST to the one which you don't want and it will usually show what was requiring the wrong one to be built (if it isn't as simple as P_V being set as mentioned before)15:23
*** AndersD_ <AndersD_!~AndersD@h-17-226.A137.corp.bahnhof.se> has quit IRC15:30
*** tedfernau <tedfernau!~tedfernau@c-76-104-226-12.hsd1.wa.comcast.net> has joined #yocto15:31
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has joined #yocto15:32
Blackbettyqschulz: didnt find anything with grep15:34
*** ENPJ <ENPJ!~ENPJ@2001:a61:24aa:d201:a9f0:885a:b6b3:4a54> has quit IRC15:34
*** mattsm <mattsm!~mattsm@104-181-154-57.lightspeed.austtx.sbcglobal.net> has joined #yocto15:36
Blackbettysetting PREFERRED_VERSION_libunwind="1.0" selects the desired recipe though15:36
*** gpanders <gpanders!~gpanders@gateway/tor-sasl/gpanders> has joined #yocto15:38
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has quit IRC15:39
Blackbettyok, the problem is visible also with other recipes, for some reason the layers priority doesnt work15:44
*** ThomasD13 <ThomasD13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC15:45
*** sstiller <sstiller!~sstiller@p200300f07f121d00044444c1f74b03fb.dip0.t-ipconnect.de> has quit IRC15:47
*** dreyna <dreyna!~dreyna@2601:646:4201:e280:9889:cc46:109e:bc51> has joined #yocto15:51
*** hpsy <hpsy!~hpsy@197.37.11.248> has joined #yocto15:53
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has joined #yocto15:54
yatesis there a recipe to buld just the "toolchain", i.e., the base (cross-) assembler, linker, gcc, libc, etc?16:12
yatesbuild16:12
LetoThe2ndyates: meta-toolchain. (didn't you ask that a couple of times already?)16:13
*** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has joined #yocto16:13
yatesLetoThe2nd: yes, you are right. just double-checking16:14
*** jUnG3 <jUnG3!3e6041d4@62.96.65.212> has quit IRC16:15
LetoThe2ndyates: i have to admit that i already think twice usually before i type something into your direction. double-checking this way in is essentially willfully wasting the time of people who are helping you out for free here, because you expect them to answer (again). have to admit more, will thinkthrice before typing now.16:16
yatesLetoThe2nd: i apologize for that - i never meant to waste your time. the problem is on my side - sometimes if i can't see the destination i want to reach i backup and re-affirm my assumptions16:19
yatesto be explicit, in this case, i have forgotten, or at least misunderstood, the role the classes play and did not realize that, apparently, the main work (at least for the default poky builds) is done by meta/classes/populate_sdk_base.bbclass16:21
*** B0ned1ger2 <B0ned1ger2!~B0ned1ger@78-63-48-72.static.zebra.lt> has joined #yocto16:21
yatesi am relearning yocto/poky - worked with it quite a bit 2-4 years ago..16:21
yatesi've forgotten more than most people ever know about yocto...16:22
*** B0ned1ger <B0ned1ger!~B0ned1ger@82-135-139-249.static.zebra.lt> has quit IRC16:25
yatesLetoThe2nd: peace, brother?16:26
*** B0ned1ger2 <B0ned1ger2!~B0ned1ger@78-63-48-72.static.zebra.lt> has quit IRC16:27
LetoThe2ndi am peaceful, just trying to make you think. and i kind of doubt your last claim, to be honest.16:27
LetoThe2ndanyways. this day is over for me16:28
LetoThe2ndhave fun y'all16:28
yatesmost people have no idea what yocto is, so that bar is pretty low16:29
Spoostercan confirm, have a yocto, still learning16:29
yatesSpooster: +116:30
SpoosterAfter switching to wayland/weston. It appears that /usr/bin/sudo just "went away" *gestures wildly16:49
SpoosterI'm guessing something in X was previously depending or pulling that down... but am I missing something simple or immediately obvious?16:49
JPEWSpooster: I would guess your hunch is correct16:50
*** MartinH97 <MartinH97!2edfa3d6@HSI-KBW-46-223-163-214.hsi.kabel-badenwuerttemberg.de> has quit IRC16:53
*** nemgti-og <nemgti-og!nemgti-og@gateway/vpn/protonvpn/nemgti-og> has joined #yocto16:54
SpoosterI'm not really sure how to best search the breadth of recipes available to figure out where /usr/bin/sudo was coming from... I guess I could try parsing the dependency graph of x11-base and x11-sato to see if anything jumps out at me...16:57
SpoosterI can revert to my inner caveman and `grep /usr/bin/sudo -r .` and see what pops up16:58
SpoosterIs there a bitbake feature here that helps me?16:58
rburtonmini-x-session pulls in sudo16:58
rburtonif you want it, just add it to your image16:58
SpoosterI likely don't want mini-x-session... but... I mean... I'm not going to be surprised there's a recipe just called `sudo` here...16:59
rburtonyes, there is a recipe called sudo16:59
rburtonhttps://layers.openembedded.org/layerindex/branch/master/recipes/?q=sudo17:00
kergothoe-pkgdata-util would tell you where it came from if you have the build17:00
kergothif you're in the image and have package-management installed, you can query the package manager17:00
kergothbitbake -g will tell you what recipes go into building the image, etc17:00
kergoththere are options17:00
kergothand yeah, layer index is awesome17:00
kergothrburton: i kind of wish there was a way to contribute pkgdata information to the layer index in some fashion, to make it possible to search runtime package names and target paths17:01
SpoosterOoo, I think layerindex was what I was hoping to find!17:01
rburtonkergoth: yes17:01
rburtonthere was the plan of just doing a build with qemux86 to at least get the basics in17:01
kergothobviously it'd vary with build configuration and stuff, but even if it could gather the info in *some* way and flag it17:01
kergothah, yeah, that'd do17:01
*** bonettor <bonettor!5e2479d3@94-36-121-211.adsl-ull.clienti.tiscali.it> has quit IRC17:03
*** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has quit IRC17:10
*** Blackbetty <Blackbetty!540affd6@84-10-255-214.static.chello.pl> has quit IRC17:11
*** gsalazar <gsalazar!~gsalazar@173.111.90.149.rev.vodafone.pt> has joined #yocto17:20
*** hpsy <hpsy!~hpsy@197.37.11.248> has quit IRC17:22
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has quit IRC17:23
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto17:24
*** vineela <vineela!~vtummala@134.134.139.83> has joined #yocto17:26
*** tedfernau <tedfernau!~tedfernau@c-76-104-226-12.hsd1.wa.comcast.net> has quit IRC17:31
*** mihai- <mihai-!~mihai@unaffiliated/mihai> has joined #yocto17:32
*** mihai- <mihai-!~mihai@unaffiliated/mihai> has quit IRC17:33
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC17:35
*** ebail <ebail!~ebail@alille-157-1-119-102.w92-131.abo.wanadoo.fr> has quit IRC17:41
*** Kyubi <Kyubi!~Kyubi@149.199.62.130> has quit IRC17:43
*** fl0v0 <fl0v0!~fvo@i5E86AD7E.versanet.de> has quit IRC17:49
*** vineela <vineela!~vtummala@134.134.139.83> has quit IRC17:56
*** frsc <frsc!~frsc@i59F72043.versanet.de> has quit IRC18:04
*** davisr <davisr!~davisr@cpe-70-92-166-130.wi.res.rr.com> has joined #yocto18:05
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC18:06
*** ebail <ebail!~ebail@2a01cb089000af0066e10f1f946ec5ec.ipv6.abo.wanadoo.fr> has joined #yocto18:18
*** nemgti-og <nemgti-og!nemgti-og@gateway/vpn/protonvpn/nemgti-og> has quit IRC18:20
*** vineela <vineela!~vtummala@134.134.139.83> has joined #yocto18:20
*** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has joined #yocto18:23
*** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has quit IRC18:28
*** ebail <ebail!~ebail@2a01cb089000af0066e10f1f946ec5ec.ipv6.abo.wanadoo.fr> has quit IRC18:32
*** Yumasi <Yumasi!~guillaume@40.72.95.92.rev.sfr.net> has quit IRC18:35
*** tlwoerner_ <tlwoerner_!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has joined #yocto18:38
*** vineela <vineela!~vtummala@134.134.139.83> has quit IRC18:46
*** tlwoerner <tlwoerner!~tlwoerner@unaffiliated/tlwoerner> has quit IRC18:46
*** tlwoerner_ <tlwoerner_!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has quit IRC18:49
*** tlwoerner <tlwoerner!~tlwoerner@unaffiliated/tlwoerner> has joined #yocto18:50
*** Kyubi <Kyubi!~Kyubi@149.199.62.129> has joined #yocto18:50
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/irccloud.com/x-rwztvrrdsnxovcja> has quit IRC18:53
*** yannholo <yannholo!~yannholo@fs-141-0-205-41.fullsave.info> has quit IRC18:54
*** ncaidin_lf <ncaidin_lf!a2fa0254@162.250.2.84> has quit IRC18:58
*** ebail <ebail!~ebail@2a01cb089000af0066e10f1f946ec5ec.ipv6.abo.wanadoo.fr> has joined #yocto19:00
*** tnovotny <tnovotny!~tnovotny@ip-78-45-64-220.net.upcbroadband.cz> has quit IRC19:03
*** tedfernau <tedfernau!~tedfernau@c-76-104-226-12.hsd1.wa.comcast.net> has joined #yocto19:03
vdlfor the image-container.bbclass, shouldn't we set hostname_pn-base-files = "" as the doc states "Having no default hostname in the filesystem is suitable for environments that use dynamic hostnames such as virtual machines."19:06
*** vineela <vineela!vtummala@nat/intel/x-dznoripdihqlzkou> has joined #yocto19:25
*** ebail <ebail!~ebail@2a01cb089000af0066e10f1f946ec5ec.ipv6.abo.wanadoo.fr> has quit IRC19:35
*** RzR <RzR!~rzr@unaffiliated/rzr> has quit IRC19:38
*** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has joined #yocto19:41
*** ebail <ebail!~ebail@2a01cb089000af0066e10f1f946ec5ec.ipv6.abo.wanadoo.fr> has joined #yocto19:43
*** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has quit IRC19:46
*** sgw <sgw!~sgw@2601:642:c400:ecf0:8107:db68:5adf:8d02> has quit IRC19:58
*** sgw <sgw!~sgw@2601:642:c400:ecf0:e84a:317d:c341:256c> has joined #yocto20:03
*** sakoman <sakoman!~steve@72.173.249.164> has quit IRC20:06
*** ENPJ <ENPJ!~ENPJ@2001:a61:3a33:7901:a9f0:885a:b6b3:4a54> has joined #yocto20:11
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC20:11
*** sakoman <sakoman!~steve@72.173.249.164> has joined #yocto20:22
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto20:25
*** vineela <vineela!vtummala@nat/intel/x-dznoripdihqlzkou> has quit IRC20:27
*** rcoote <rcoote!~rcoote@2a02:908:692:81c0:44dc:84ad:f7d8:ff52> has quit IRC20:30
*** ebail <ebail!~ebail@2a01cb089000af0066e10f1f946ec5ec.ipv6.abo.wanadoo.fr> has quit IRC20:33
*** bps <bps!~bps@80.71.142.18> has quit IRC20:34
*** aleblanc <aleblanc!~textual@192-222-183-114.qc.cable.ebox.net> has joined #yocto20:42
*** om26er <om26er!6e260b11@ubuntu/member/om26er> has joined #yocto20:50
*** agust <agust!~agust@p508b6964.dip0.t-ipconnect.de> has quit IRC20:55
*** gillesMMM <gillesMMM!~gm@117.187.22.109.rev.sfr.net> has joined #yocto20:59
*** jdrol <jdrol!~gm@117.187.22.109.rev.sfr.net> has quit IRC21:00
*** gillesMMM <gillesMMM!~gm@117.187.22.109.rev.sfr.net> has quit IRC21:00
*** ebail <ebail!~ebail@2a01cb089000af0066e10f1f946ec5ec.ipv6.abo.wanadoo.fr> has joined #yocto21:01
*** berton <berton!~user@200-180-244-11.user3p.brasiltelecom.net.br> has quit IRC21:10
*** sakoman1 <sakoman1!~steve@72.173.249.164> has joined #yocto21:11
*** beneth <beneth!~beneth@irc.beneth.fr> has left #yocto21:14
*** sakoman <sakoman!~steve@72.173.249.164> has quit IRC21:14
*** sbach <sbach!~sbachmatr@192.184.90.156> has quit IRC21:18
*** sbach <sbach!~sbachmatr@192.184.90.156> has joined #yocto21:19
yatesis there a specification or description of .bbclass files? for example, i see common python-type functions "def populate_sdk_command(d):" and also other thingies lime "fakeroot python do_populate_sdk() {...}21:29
yatess/lime/like21:29
yatesgoogled around and did not see this anywhere obvious21:29
rburtondid you try https://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-user-manual.html#bitbake-user-manual-metadata21:32
rburtondef and python are subtly different for historical reasons but are just ways to write python functions21:32
yatesrburton: ok, but what is "xyz python abc() {...}"? as in "fakeroot python do_populate_sdk() {...}"?21:36
yatesline 171 of poky/meta/classes/populate_sdk_base.bbclass21:38
*** ebail <ebail!~ebail@2a01cb089000af0066e10f1f946ec5ec.ipv6.abo.wanadoo.fr> has quit IRC21:38
*** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has joined #yocto21:43
kergothyates: fakeroot flags the task to be run under fakeroot/pseudo. it literally just sets a flag 'fakeroot' to 1 on the task in the metadata, same thing the python keyword does21:44
*** jdrol <jdrol!~gm@117.187.22.109.rev.sfr.net> has joined #yocto21:45
jdrolhi I don't understand the rule of pn in hostname_pn-base-files = "mybox" ... can you explain me ?21:46
*** B0ned1ger <B0ned1ger!~B0ned1ger@78-63-48-72.static.zebra.lt> has quit IRC21:47
*** prabhakarlad <prabhakarlad!51988ebd@host81-152-142-189.range81-152.btcentralplus.com> has quit IRC21:49
*** bobo <bobo!~bobo@customer-145-14-101-3.stosn.net> has joined #yocto21:51
*** McAwesome <McAwesome!b0c6c9d4@ip-176-198-201-212.hsi05.unitymediagroup.de> has joined #yocto21:52
McAwesomehey, can I add a recipe to my system without having to building the image again?21:53
JPEWMcAwesome: You can build build a package (ipk, deb, rpm) and install it if the tools are on the image22:07
JPEWMcAwesome: I'm... not sure how, we build read-only images so it's always a full update to change it, but I know it's possible22:07
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC22:17
McAwesomeJPEW thanks for thw quick answer, do you know how can i know what packing mechanism does my system use?22:19
JPEWMcAwesome: Check the `PACKAGE_CLASSES` variable22:20
JPEWbitbake -e | grep ^PACKAGES_CLASSES=22:20
JPEWMcAwesome: It doesn't really matter *which* one you are using, it would only affect which tool (dnf, apt, opkg) you would use to install the package22:21
JPEWMcAwesome: Bitbake will build a recipe to match whatever your system is already using (unless you change it)22:21
McAwesomeJPEW bitbake -e | grep ^PACKAGES_CLASSES= gives no output22:26
McAwesomeJPEW after installing opkg how can i then add glew for example without having to re-build the image?22:27
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto22:31
JPEWMcAwesome: I think you can copy over the ipk file and use opkg to install it22:32
JPEWAfter you have built glew from a recipe of course22:32
JPEWMcAwesome: I think that you can also tell bitbake to make a valid package feed that you could server over HTTP and have the target pull from it.... but I'm not sure on the details22:33
McAwesomesorry for my newbie questions but what do you mean built  glew from the recipe?  @jpew22:39
McAwesomelike I can see the recipe file and download it from the sources22:44
McAwesomeJPEW22:57
*** ssajal <ssajal!~ssajal@bras-base-otwaon1146w-grc-06-184-146-108-8.dsl.bell.ca> has quit IRC23:02
*** opello_ is now known as opello23:03
*** psnsilva <psnsilva!~psnsilva@161.230.35.203> has quit IRC23:12
*** psnsilva <psnsilva!~psnsilva@161.230.35.203> has joined #yocto23:12
*** sakoman1 <sakoman1!~steve@72.173.249.164> has quit IRC23:14
*** hackspider <hackspider!5dec023e@p5dec023e.dip0.t-ipconnect.de> has joined #yocto23:26
*** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC23:26
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto23:29
*** ENPJ <ENPJ!~ENPJ@2001:a61:3a33:7901:a9f0:885a:b6b3:4a54> has quit IRC23:33
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC23:33
*** sakoman <sakoman!~steve@72.173.249.164> has joined #yocto23:34
*** hackspider <hackspider!5dec023e@p5dec023e.dip0.t-ipconnect.de> has quit IRC23:48
*** psnsilva <psnsilva!~psnsilva@161.230.35.203> has quit IRC23:57

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!