Wednesday, 2021-02-03

*** rperier_ <rperier_!> has joined #yocto00:05
*** B0ned1ger <B0ned1ger!> has joined #yocto00:07
*** Gintaro_ <Gintaro_!> has joined #yocto00:07
*** Gintaro <Gintaro!> has quit IRC00:11
*** rperier <rperier!~quassel@unaffiliated/bambee> has quit IRC00:11
*** B0ned1ger <B0ned1ger!> has quit IRC00:11
*** Minjae_Kim49 <Minjae_Kim49!1b7af247@gateway/web/cgi-irc/> has joined #yocto00:13
*** camus <camus!~Instantbi@> has joined #yocto00:26
*** kaspter <kaspter!~Instantbi@> has quit IRC00:26
*** camus is now known as kaspter00:26
*** leon-anavi <leon-anavi!~Leon@> has quit IRC00:28
*** cp-- <cp--!> has quit IRC00:50
*** cp- <cp-!> has joined #yocto00:51
*** bobo <bobo!> has quit IRC01:04
*** tgoodwin <tgoodwin!> has joined #yocto01:09
*** kiwi_29 <kiwi_29!> has quit IRC01:13
*** kiwi_29 <kiwi_29!> has joined #yocto01:14
*** kiwi_29 <kiwi_29!> has quit IRC01:20
*** kiwi_29 <kiwi_29!> has joined #yocto01:21
khemRP:  I think I have kernel issue under control sent a v2 of binutils patchset01:41
*** kiwi_29 <kiwi_29!> has quit IRC01:55
*** B0ned1ger <B0ned1ger!> has joined #yocto02:08
*** B0ned1ger <B0ned1ger!> has quit IRC02:13
*** B0ned1ger <B0ned1ger!> has joined #yocto02:16
*** kiwi_29 <kiwi_29!> has joined #yocto02:18
*** tgoodwin <tgoodwin!> has quit IRC02:20
*** dvhart <dvhart!~dvhart@> has quit IRC02:21
*** B0ned1ger <B0ned1ger!> has quit IRC02:21
*** sakoman <sakoman!~steve@> has quit IRC02:35
*** kiwi_29 <kiwi_29!> has quit IRC02:40
*** kiwi_29 <kiwi_29!> has joined #yocto02:40
*** vineela <vineela!~vtummala@> has quit IRC02:42
*** tgoodwin <tgoodwin!> has joined #yocto02:44
*** tgoodwin <tgoodwin!> has quit IRC02:46
*** kiwi_29 <kiwi_29!> has quit IRC02:50
*** kiwi_29 <kiwi_29!> has joined #yocto02:50
*** timblechmann <timblechmann!~quassel@2001:f40:906:68cb:a6a3:4f61:aa03:18af> has quit IRC02:52
*** sakoman <sakoman!~steve@> has joined #yocto02:57
*** kiwi_29 <kiwi_29!> has quit IRC03:02
*** ahadi <ahadi!~ahadi@> has quit IRC03:06
*** ahadi <ahadi!> has joined #yocto03:08
*** dvhart <dvhart!~dvhart@> has joined #yocto03:21
*** RzR <RzR!~rzr@unaffiliated/rzr> has quit IRC03:24
paulg...never say you have something solved late in the day on Groundhog Day.03:24
*** dvhart <dvhart!~dvhart@> has quit IRC03:25
*** kiwi_29 <kiwi_29!> has joined #yocto03:26
*** kiwi_29 <kiwi_29!> has quit IRC03:30
*** kiwi_29 <kiwi_29!> has joined #yocto03:31
*** camus <camus!~Instantbi@> has joined #yocto03:50
*** kaspter <kaspter!~Instantbi@> has quit IRC03:51
*** camus is now known as kaspter03:51
*** bobo <bobo!> has joined #yocto03:54
*** kiwi_29 <kiwi_29!> has quit IRC03:54
*** kiwi_29 <kiwi_29!> has joined #yocto03:55
*** kiwi_29 <kiwi_29!> has quit IRC04:08
*** kiwi_29 <kiwi_29!> has joined #yocto04:10
*** kpo_ <kpo_!> has quit IRC04:14
*** kpo_ <kpo_!> has joined #yocto04:15
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC04:16
*** thaytan <thaytan!~thaytan@> has quit IRC04:30
*** oberstet <oberstet!~oberstet@> has joined #yocto04:30
*** thaytan <thaytan!~thaytan@> has joined #yocto04:32
*** bobo <bobo!> has quit IRC04:44
*** camus <camus!~Instantbi@> has joined #yocto04:53
*** kaspter <kaspter!~Instantbi@> has quit IRC04:53
*** camus is now known as kaspter04:53
*** amitk <amitk!~amit@unaffiliated/amitk> has joined #yocto04:53
*** kiwi_29 <kiwi_29!> has quit IRC04:57
*** sakoman <sakoman!~steve@> has quit IRC04:58
*** kiwi_29 <kiwi_29!> has joined #yocto05:04
*** dreyna <dreyna!> has quit IRC05:04
*** w00die <w00die!~w00die@> has quit IRC05:05
*** w00die <w00die!~w00die@> has joined #yocto05:07
*** kiwi_29 <kiwi_29!> has quit IRC05:11
*** kiwi_29 <kiwi_29!> has joined #yocto05:24
*** feddischson <feddischson!> has joined #yocto05:25
*** alessioigor <alessioigor!> has joined #yocto05:54
*** alessioigor <alessioigor!> has quit IRC06:07
*** tlwoerner <tlwoerner!~tlwoerner@unaffiliated/tlwoerner> has quit IRC06:11
*** B0ned1ger <B0ned1ger!> has joined #yocto06:18
*** beneth <beneth!> has joined #yocto06:21
*** B0ned1ger <B0ned1ger!> has quit IRC06:22
kiwi_29Hello.. I have a third party recipe here which uses PV = in recipe name . This is too old06:31
kiwi_29How do I make sure to get latest source with PV =
kiwi_29is there a way to write bbappend ?06:32
*** AndersD <AndersD!> has joined #yocto06:32
*** bobo <bobo!> has joined #yocto06:35
*** bobo__ <bobo__!> has joined #yocto06:37
*** jobroe <jobroe!> has joined #yocto06:48
*** tlwoerner <tlwoerner!~tlwoerner@unaffiliated/tlwoerner> has joined #yocto06:57
*** sno <sno!> has quit IRC07:14
*** B0ned1ger <B0ned1ger!> has joined #yocto07:15
*** sno <sno!> has joined #yocto07:19
*** jobroe <jobroe!> has quit IRC07:23
*** jobroe <jobroe!> has joined #yocto07:24
*** goliath <goliath!> has joined #yocto07:34
*** frsc <frsc!> has joined #yocto07:41
RobertBerger@kiwi_29: I would just write a new recipe s6_2.10.0.1.bb07:41
kiwi_29hi RobertBerger ..thank you :)  .. I just wrote one and currently debugging errors ..phew07:42
RobertBerger@kiwi_29: I hope you enjoy ;) That's always fun.07:42
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto07:43
RobertBerger@kiwi_29: and once you get it to run, I guess you will have even more fun integrating it, I guess, if I understand correctly what it does07:45
*** kpo_ <kpo_!> has quit IRC07:46
*** B0ned1ger <B0ned1ger!> has quit IRC07:46
kiwi_29yes... its a mess ..trying to get it to work somehow07:46
*** B0ned1ge_ <B0ned1ge_!> has joined #yocto07:46
RobertBergerso you are after a really small system it seems07:47
*** kpo_ <kpo_!> has joined #yocto07:47
*** B0ned1ger2 <B0ned1ger2!> has quit IRC07:47
RPkhem: looks like the glibc patch needs attention :/07:48
*** rcoote <rcoote!> has joined #yocto07:50
kiwi_29RobertBerger ...thats correct07:52
*** mckoan|away is now known as mckoan07:54
*** Js <Js!> has joined #yocto07:55
*** Js is now known as Guest8987207:56
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/> has joined #yocto07:57
*** fl0v0 <fl0v0!~fvo@> has joined #yocto07:58
*** bobo__ <bobo__!> has quit IRC07:59
*** bobo <bobo!> has quit IRC07:59
*** B0ned1ger <B0ned1ger!> has joined #yocto07:59
*** B0ned1ge_ <B0ned1ge_!> has quit IRC08:02
*** B0ned1ger <B0ned1ger!> has quit IRC08:03
*** B0ned1ger <B0ned1ger!> has joined #yocto08:07
*** Guest89872 <Guest89872!> has quit IRC08:10
*** kiwi_29 <kiwi_29!> has quit IRC08:21
*** kiwi_29 <kiwi_29!> has joined #yocto08:22
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto08:33
*** camus <camus!~Instantbi@> has joined #yocto08:36
*** kaspter <kaspter!~Instantbi@> has quit IRC08:37
*** camus is now known as kaspter08:37
*** rcoote <rcoote!> has quit IRC08:37
*** kiwi_29 <kiwi_29!> has quit IRC08:38
*** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:572d:5f36:41d6:1475> has joined #yocto08:47
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto08:59
kayterinaI think my build takes a lot time, is there something in the configs I might set? for linux-yocto-tiny-5.1009:02
*** BobPungartnik <BobPungartnik!~BobPungar@> has joined #yocto09:05
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto09:05
*** BobPungartnik <BobPungartnik!~BobPungar@> has quit IRC09:06
*** B0ned1ger <B0ned1ger!> has quit IRC09:09
*** B0ned1ger2 <B0ned1ger2!> has quit IRC09:10
*** zkrx <zkrx!> has quit IRC09:11
qschulzkayterina: define "a lot of time" and on which machine you're building09:11
*** dreyna <dreyna!> has joined #yocto09:28
*** dreyna <dreyna!> has joined #yocto09:29
*** kiwi_29 <kiwi_29!> has joined #yocto09:38
*** B0ned1ger <B0ned1ger!> has joined #yocto09:40
*** zkrx <zkrx!> has joined #yocto09:40
*** kiwi_29 <kiwi_29!> has quit IRC09:44
*** manuel1985 <manuel1985!> has joined #yocto09:51
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto09:54
*** B0ned1ger <B0ned1ger!> has quit IRC09:57
*** B0ned1ger2 <B0ned1ger2!> has quit IRC10:02
*** B0ned1ger <B0ned1ger!> has joined #yocto10:05
kayterinaI stopped the build and didn't complete. It was over 2 hours for bitbake virtual/kernel and it started at 46% from where I stopped it yesterday. The machine has an i7-10700 CPU @ 2.90GHz10:14
kayterina46% of the linux-yocto-tiny, not the whole tasks10:15
*** yann <yann!~yann@> has quit IRC10:18
*** dreyna <dreyna!> has quit IRC10:30
manuel1985Hello all! A few people in my team would like to include a python project in Yocto. The Python project has its dependencies in a requirement.txt. I know that The Right Way(tm) would be to move over the dependencies to the RDEPENDS variable in the recipe, but they want to keep them there. (For development outside Yoct I suppose.)10:30
manuel1985Can you have Yocto read and respect that requirements.txt somewhow?10:30
mcfriskmanuel1985: requirements.txt is for pip, it doesn't use yocto or host package system to satisfy dependencies. So I'd say no, requirements.txt can not be used directly. You can use it to fill in bitbake recipe DEPENDS and RDEPENDS fields though, but need to manually check that versions are compatible.10:33
manuel1985mcfrist: By "you can use it" you mean automatically? Like, is there some tool I can leverage for this?10:34
RPmanuel1985: there is no official supported mechanism, no. You may see if devtool can correctly build a recipe for your project and then script around that to regenerate the recipe. I don't know if it will work or not though10:37
manuel1985RP: I see, thanks10:40
*** RzR <RzR!~rzr@2a01:e34:ec57:d710:a9dd:80f3:da3:2d3c> has joined #yocto10:40
*** RzR <RzR!~rzr@unaffiliated/rzr> has joined #yocto10:40
qschulzkayterina: that does not seem correct indeed. Usually it's a good thing to look at what the current process is doing (the PID is printed on the bitbake output), to check if it's hung somewhere10:40
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto10:45
malinusi5-2500k@4.2Ghz, took 4h + 2h for the sdk. Not bad considering I've got a load of crap into that image.10:46
kayterinain my preious job I built on my laptop with a i3/8gb, here they got me a deeloper's machine, I am expecting miracles10:46
*** intera91 <intera91!> has joined #yocto10:47
malinusheh I'm just building on my own desktop, since working from home10:47
kayterinaha,you should pay tax for the gas you are not consuming!10:48
kayterina(or was it in the preious quarantine?)10:48
*** NiksDev <NiksDev!~NiksDev@> has quit IRC10:48
kayterinaanyways, I found a bsp from the vendor with a 3.4, can I use its u-boot and dtb with the linux-yocto 5.4/sunxi_defconfig?10:49
qschulzkayterina: why would you take a 3.4 kernel?10:51
qschulzand no, you cannot take the defconfig from 5.4 kernel10:51
qschulzkayterina: check if your machine is still doing something with `top` or `htop` and check the output of the process with `PID=20151; tail -f /proc/$PID/fd/2`10:53
qschulz(change the PID obviously)10:53
qschulzwas it 2h for only virtual/kernel or for the whole build?10:53
kayterinabitbake virtual/kernel , wait I'll run the commands10:53
kayterinaI ran again bitbake virtual/kernel and in another terminal  `PID=31806; tail -f /proc/$PID/fd/2` it is blank. No errors?10:57
kayterinablank=no output on terminal,blinking cursor10:57
malinus"3.4 vendor kernel". kayterina - Show me where they hurt you :(10:58
malinusKyubi: on a serious note, what kind of board are you guys using?10:59
*** minimaxwell <minimaxwell!> has quit IRC10:59
qschulzmalinus: bpi-m2 zero IIRC, just old Allwinner boards didn't have decent BSP support from the vendor.11:00
qschulzkayterina: the PID corresponded to which task? and sometimes you got to wait a bit11:01
*** minimaxwell <minimaxwell!> has joined #yocto11:01
qschulzah I bet it's during the fetch task?11:02
qschulzgit isn't very verbose while fetching very big repos11:02
qschulzyou can also read the logs still with tail -f from ${WORKDIR}/temp/log.do_<task> (workdir being tmp/work/...../linux-yocto/5.4.../)11:04
kayterinad'gh,yes it is during do_fetch, I'll search the logs11:12
kayterinaso it is just downloading that is slow, so I leave it to finish? It says 3gb, is it networking on my side? it says11:22
kayterinaLength: 3177321323 (3.0G), 585744215 (559M) remaining [application/octet-stream]11:23
kayterinaSaving to: ‘/***/poky/build/downloads/’11:23
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto11:25
*** intera91 <intera91!> has quit IRC11:27
*** zkrx <zkrx!> has quit IRC11:29
*** amitk_ <amitk_!~amit@unaffiliated/amitk> has joined #yocto11:37
*** sno <sno!> has quit IRC11:38
*** amitk <amitk!~amit@unaffiliated/amitk> has quit IRC11:38
*** zkrx <zkrx!> has joined #yocto11:46
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto11:54
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto11:59
*** B0ned1ger <B0ned1ger!> has quit IRC12:02
*** B0ned1ger2 <B0ned1ger2!> has quit IRC12:03
*** jobroe <jobroe!> has quit IRC12:08
*** yann <yann!~yann@> has joined #yocto12:09
*** jobroe <jobroe!> has joined #yocto12:12
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto12:14
*** tgoodwin <tgoodwin!> has joined #yocto12:25
*** sno <sno!> has joined #yocto12:31
*** minimaxwell <minimaxwell!> has quit IRC12:35
*** minimaxwell <minimaxwell!> has joined #yocto12:37
*** kaspter <kaspter!~Instantbi@> has quit IRC12:40
*** kaspter <kaspter!~Instantbi@> has joined #yocto12:40
*** kpo_ <kpo_!> has quit IRC12:59
*** kpo_ <kpo_!> has joined #yocto13:00
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto13:03
*** B0ned1ger <B0ned1ger!> has joined #yocto13:36
*** B0ned1ger2 <B0ned1ger2!> has quit IRC13:39
*** Wouter01000 <Wouter01000!> has quit IRC13:39
*** Wouter01000 <Wouter01000!> has joined #yocto13:40
*** B0ned1ger <B0ned1ger!> has quit IRC13:42
*** sakoman <sakoman!~steve@> has joined #yocto14:01
*** manuel_ <manuel_!> has joined #yocto14:11
*** B0ned1ger <B0ned1ger!> has joined #yocto14:12
*** manuel1985 <manuel1985!> has quit IRC14:14
JPEWhalstead: Do you have some time to sort out that reproducibility page with me?14:19
kayterinaare dts and dtsi appended to the kernel recipe or uboot?14:21
*** minimaxwell <minimaxwell!> has quit IRC14:24
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto14:25
*** minimaxwell <minimaxwell!> has joined #yocto14:26
*** Lihis <Lihis!> has quit IRC14:35
*** Lihis <Lihis!~Lihis@2001:41d0:e:f34::1> has joined #yocto14:37
*** stephano <stephano!~stephano@> has joined #yocto14:53
*** medaliyou <medaliyou!29e3fbc9@> has joined #yocto14:53
LetoThe2ndkayterina: what do you mean?14:55
*** sno <sno!> has quit IRC14:56
medaliyouHello Guys, Hope you all are doing well ...14:56
medaliyouHow to make a binary or a script (ELF or whatever) be included with image whenever i bitbake it ? Let's say i cross compiled things and ii want them to be automatically included (copied) to /usr/bin/${ELF-NAME} everytime i create the image ?14:58
*** NiksDev <NiksDev!~NiksDev@> has quit IRC14:59
*** B0ned1ger <B0ned1ger!> has quit IRC15:00
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto15:00
LetoThe2ndmedaliyou: but note, usually its better to actually write a recipe that properly does the compilation inside the build process.15:03
*** joeythes- is now known as joeythesaint15:03
alephanmoto-timo: Hello. I have a short question about `meta-python` do you accept some python modules which are present in v>dunfell but are needed for other layers, backported to dunfell?15:05
*** zyga_ <zyga_!~zyga@unaffiliated/zyga> has joined #yocto15:05
alephannamely: python3-betamax, python3-mccabe, python3-mock, python3-pep8 and python3-requests-toolbelt15:06
alephanMainly because that's an LTS and these are needed as dependencies for other layers (for example homeassistant)15:06
medaliyouas i asked before,  i ve to optimize boot-time, so is it better to cross compile a big QT project or to install a QT layer and recipes ??? Does it affect system boot time that much ?15:06
alephanmoto-timo: I'm willing to push patches and test so I don't have to maintain them as a separate temporary layer15:08
qschulzkayterina: uboot and kernel have device trees support but they can (and often are) different15:09
LetoThe2ndmedaliyou: why should the boot time of your device be affected by where you compiled the application? the device runs a binary.15:09
*** Lihis <Lihis!~Lihis@2001:41d0:e:f34::1> has quit IRC15:10
*** jobroe <jobroe!> has quit IRC15:10
kayterinaI want to build for bpi zero with latest kernel. How do I provide the device tree?15:11
moto-timoalephan: generally we do not add anything new to a stable branch15:11
*** dleppich <dleppich!~Thunderbi@> has quit IRC15:11
medaliyoui mean booting a small FS is faster than a larger one ?15:11
LetoThe2ndmedaliyou: and why do you think manually crosscompiling and packaging makes the FS smaller?15:12
*** Lihis <Lihis!> has joined #yocto15:12
moto-timoalephan: but dunfell is the first LTS, so it is worth discussing with the OE TSC.15:13
*** dleppich <dleppich!> has joined #yocto15:13
alephanmoto-timo: Yes. That's exactly why I'm asking. I hope we can push them due to that being an LTS.15:13
medaliyouplease excuse me if i'm not asking things well, i'm an amateur & still learning, but from what i understand buidling a linux containing a QT layer (various libQTs) is gonna take much time to boot VS a linux containg only some binaries in /bin ???15:14
moto-timoalephan: you must ask OE TSC. It is a deviation from stable branch policy.15:14
LetoThe2ndalephan: moto-timo: i would rather vote for a form of HWE-style layer/branch. e.g., leaving dunfell untouched, but providing dunfell-enablement-backports (or comparable)15:15
LetoThe2ndmedaliyou: its not about the way you ask - i'm just trying to make you think about your own question.15:15
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC15:15
LetoThe2ndmedaliyou: hint: you are on the COMPLETELY wrong track.15:15
medaliyouhhhhhhhh, great news, HELPPPPPPPPPPPP !15:16
alephanLetoThe2nd: I can always have a separated layer which ads/does the required changes. But that was the whole idea of not having to maintain a duplication for a full LTS.15:17
LetoThe2ndmedaliyou: well, how about actually working through some of the documentation on boot time reduction? theres probably a gazillion of tutorials on youtube already.15:18
alephanIf you meant to have a additional branch in meta-oe for it, I find it a maintenance overhead just transferred to another place without any real benefit.15:18
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto15:18
kayterinaI am confused. There are at least 3 sources for the bpi images. Shouldn't I take something from them? Uboot for example? And if it is possibly to use latest kernel,why all images have 3.4 or 4.4?15:19
qschulzkayterina: the dts is already provided arch/arm/boot/dts/sun8i-h2-plus-bananapi-m2-zero.dts15:19
LetoThe2ndalephan: the point is -  from the LTS perspective, whats to be gained if we start randomly adding new packages just because "somebody depends on ot"?15:20
LetoThe2nd*it, even15:20
qschulzkayterina: because Allwinner is (was?) a very bad vendor in terms of BSP quality and updates15:20
qschulzso, board vendors using Allwinner shitty BSP probably didn't want to make more effort that this15:20
alephanThe gain is to enable it to be used on more external layers. Because LTS will be a place to stay for a good while now LetoThe2nd15:21
qschulznow, there was a huge community effort behind Allwinner SoCs that enabled the upstream linux kernel to have support for them15:21
LetoThe2ndalephan: but of course as moto-timo put it - the TSC is authoritative on that. i am not.15:21
*** zyga_ <zyga_!~zyga@unaffiliated/zyga> has quit IRC15:22
LetoThe2ndalephan: where do you end? "just new recipes".. "erm now, see, this set of recipes just needs that new class"... "ya sure, its just a tiny backport..."15:22
alephanThe alternative is for all the other people to reinvent the wheel - and that for an LTS so for a long time. I find it a bit unappealing. But I see the point15:23
LetoThe2ndalephan: an LTS will inevitably age and need more and more massaging to be used on new things. and no, nobody needs to reinvent anything. it can all be done just the way you worded it. just not in the core layer. but thats what we have layers for, right? just make a meta-python-lts-special-sauce that you can share. zero reinvention.15:24
LetoThe2ndone of the reasons why an LTS isn't an idea as good as it sounds.15:25
kayterinahm.interesting. So I am left with the machine.conf.  where is the path with available tunes? I suppose there will be one for sun8iw?15:26
alephanLetoThe2nd: Sure. That was indeed the initial idea. I will stick to that for now.15:27
LetoThe2ndalephan: :) but of course, please take it to the TSC nonetheless. its always good to have opinions, and eventually a decision that can be referred to!15:30
qschulzkayterina: I wouldn't take inspiration from meta-sunxi as they decided to go with one tune, the common denominator between all supported machines, which means it won't squeeze as much as possible from your HW15:30
alephan@LetoThe2nd I think your point was clear and I tend to agree generally with it when wearing the maintainer/LTS hat. From the user perspective I was trying an easier way forward though.15:31
alephanThanks LetoThe2nd and moto-timo15:31
LetoThe2ndalephan: thanks for the input!15:32
*** King_InuYasha is now known as Conan_Kudo15:35
*** Conan_Kudo is now known as King_InuYasha15:35
alephanLetoThe2nd: I just realized with whom I just talked. Prost!15:45
*** manuel_ <manuel_!> has quit IRC15:50
*** AndersD <AndersD!> has quit IRC15:51
*** King_InuYasha is now known as Conan_Kudo15:51
*** Conan_Kudo is now known as King_InuYasha15:52
LetoThe2ndalephan: hehe, prost!15:53
*** dvhart <dvhart!~dvhart@> has joined #yocto15:53
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC15:54
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto15:55
*** B0ned1ger <B0ned1ger!> has joined #yocto15:59
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC16:02
*** B0ned1ger2 <B0ned1ger2!> has quit IRC16:03
*** dvorkindmitry <dvorkindmitry!~dv@> has quit IRC16:05
*** leon-anavi <leon-anavi!~Leon@> has quit IRC16:05
*** kpo_ <kpo_!> has quit IRC16:05
*** B0ned1ger <B0ned1ger!> has quit IRC16:05
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto16:06
*** kpo_ <kpo_!> has joined #yocto16:06
*** B0ned1ger <B0ned1ger!> has joined #yocto16:07
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto16:12
*** B0ned1ger <B0ned1ger!> has quit IRC16:16
*** B0ned1ger2 <B0ned1ger2!> has quit IRC16:17
khemRP:  yeah I think the binutils patch series touches glibc as well and so they need to be sequenced16:20
RPkhem: oh, I understand now :/16:22
khemRP:  I will have to send v2 anyway so lets get the binutils settled first16:22
RPkhem: we'll need a new uninative release once we get glibc in16:22
khemRP: one issue I am seeing is due to hwcaps introduction in glibc 2.3316:22
RPkhem: ok. I'm worried about the wic failure on the AB and whether its from binutils or not16:23
khemour tuning for qemux86-64 is core2duo and glibc ldso does not lilke it16:23
khemrecipe-sysroot//lib/ CPU ISA level is lower than required16:23
khemif I use -cpu Nehalem instead of -cpu core2duo then it works ok16:24
khemthis is when runing qemu usermode16:24
RPkhem: hmm, interesting :/16:24
RPkhem: the initramfs issue is due to things like pxeboot.img in grub growing to 132MB in size with loads of zero padding16:28
RPkhem: looks bintutils to me16:28
khemso one option is to change using -cpu core2duo in machine conf for qemu other option perhaps is to bump qemu defaulttune to corei7-6416:28
*** minimaxwell <minimaxwell!> has quit IRC16:29
khemyeah its likely due to linker perhaps but can we know which given  binary is causing it ?16:30
*** minimaxwell <minimaxwell!> has joined #yocto16:31
RPkhem: maybe?16:33
RPkhem: glibc effectively dropped support for older x86 cpus?16:34
khemRP:  yeah that grub patch looks promising, has got changes to support the x86-64 ISA levels in 2.3316:35
khemI dont think its dropped but defaults have changed somehow16:36
RPkhem: I applied locally and the 132MB file is now 1024 bytes :)16:37
RPkhem: and confirmed it fixed the issue with the initramfs locally16:38
RPkhem: we can have another pass at building with these pieces included16:38
khemGNU_PROPERTY_X86_ISA version support has been added to toolchain recently which now we have for glibc and binutils with these upgrades and gcc 11 will introduce the needed -march options too16:38
khemRP: this is the patch;a=commit;h=ecce11aa0752735c4fd730da6e7c9e0b98e12fb816:42
*** ahadi <ahadi!> has quit IRC16:45
*** JaBen <JaBen!~Thunderbi@2a02:8109:86c0:1c58:bd52:f0ef:80f0:e69e> has joined #yocto16:45
*** frsc <frsc!> has quit IRC16:45
*** ahadi <ahadi!> has joined #yocto16:45
*** frsc <frsc!> has joined #yocto16:46
*** JaBen <JaBen!~Thunderbi@2a02:8109:86c0:1c58:bd52:f0ef:80f0:e69e> has quit IRC16:47
RPkhem: I guess the question is why we seem to build binaries that won't run with the qemu options they're supposed to be compatible with? :/16:47
chrysh_when I do a `devtool modify <recipe name>, and bitbake writes ERROR: Task do_patch does not exist for target <recipe name>, should I just add do_patch to the recipe by hand?16:52
qschulzchrysh_: which recipe is that?16:53
qschulzI'd assume someone did a deltask do_patch instead of do_patch[noexec] = "1"16:54
*** frsc <frsc!> has quit IRC16:54
qschulzor maybe you're trying to devtool modify an image recipe?16:55
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto16:55
chrysh_qschulz: true. it's still the gcc recipe. and yes, there is a `deltask do_patch` in
RPzeddii: thanks for the uprev, really helps!16:57
chrysh_why is that there?16:57
RPchrysh_: gcc-source provides the source code for the gcc recipes which is extracted once and shared between the gcc recipes16:58
khemRP:  thats a good question I am trying to find the answer to as well16:59
*** w00die <w00die!~w00die@> has quit IRC16:59
*** vineela <vineela!~vtummala@> has joined #yocto16:59
khemso its probing h/w for features and qemu is reporting perhaps less capabilities16:59
khemso it could be that now that ldso is doing the check17:00
chrysh_RP: still, why can't I patch them?17:00
RPchrysh_: you can in the gcc-source recipe17:00
*** w00die <w00die!~w00die@> has joined #yocto17:01
chrysh_RP: in which situation would a person want to remove a task (in gcc)?17:03
chrysh_this is how the recipe looks like. why the two ways of disabling do_fetch?17:04
qschulzchrysh_: I think the catch is that gcc is a "special" recipe because it's using the work-shared mechanism. e.g. I couldn't also build modules from a devtool modified kernel recipe IIRC.17:04
chrysh_qschulz: so if I have compile time errors and would want to fix that, how would I create the patches?17:07
RPchrysh_: you'd add them to the gcc-source recipe17:07
RPunfortunately devtool doesn't work well with gcc based recipes because it uses a shared workdir and devtool doesn't understand shared workdirs17:08
qschulzRP: yet. There's always room for improvement :)17:08
RPqschulz: well, yes. There is an open bug but we can't seem to get anyone to work on it :(17:09
qschulzchrysh_ just volonteered :D17:10
vdlSince the initramfs scripts might have hard dependency on the init manager (e.g. using systemctl switch-root), but the init manager choice is supposed to be done in the distro conf, how do you guys handle that?17:11
RPvdl: you can configure to allow sysvinit and systemd together17:17
RPjonmason: I dropped the libical upgrade from master-next due to the reproducibility issue, I've not replied on list though. The initramfs issues in selftest and wic builds are hopefully addressed by the grub patch I've sent and is in testing17:21
RP(caused by the binutils uprev)17:21
vdlRP: what if I want systemd in the initramfs?17:21
RPjonmason: the genericx86-64 failure was reported on list and Bruce's patch to meta-yocto should help17:21
RPvdl: then depend on and include it?17:21
*** mckoan is now known as mckoan|away17:22
vdlRP: from the initramfs image recipe?17:22
RPvdl: sure17:23
jonmasonRP: thanks.  Also, good reminder to get on the swat task :)17:25
*** kiwi_29 <kiwi_29!> has joined #yocto17:26
RPjonmason: I did triage one of the builds out the way for you17:28
*** vineela <vineela!~vtummala@> has quit IRC17:33
*** dallas <dallas!~dallas@> has joined #yocto17:33
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto17:34
*** Yumasi <Yumasi!~guillaume@2a01:e0a:5cb:4430:572d:5f36:41d6:1475> has quit IRC17:37
ndechey RP (or anyone else who might know!), are we doing any tests on AB to check/ensure that package versions are 'right' (increasing?) and do we test with the pr server?17:39
rburtoni think version-going-backwards is a default warning17:48
*** dallas <dallas!~dallas@> has quit IRC17:49
*** medaliyou <medaliyou!29e3fbc9@> has quit IRC17:51
*** suji <suji!c013e4fa@> has joined #yocto17:52
*** suji <suji!c013e4fa@> has quit IRC17:54
*** fl0v0 <fl0v0!~fvo@> has quit IRC17:58
*** leon-anavi <leon-anavi!~Leon@> has quit IRC18:08
*** sno <sno!> has joined #yocto18:15
*** zkrx <zkrx!> has quit IRC18:34
*** dmoseley <dmoseley!~dmoseley@> has quit IRC18:38
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC18:39
*** bobo <bobo!> has joined #yocto18:41
*** bobo__ <bobo__!> has joined #yocto18:41
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/> has quit IRC18:42
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto18:43
*** minimaxwell <minimaxwell!> has quit IRC18:43
*** minimaxwell <minimaxwell!> has joined #yocto18:44
*** zkrx <zkrx!> has joined #yocto18:59
khemRP: sent a v2 of glibc patch on top of current master-next19:00
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC19:04
*** dreyna <dreyna!> has joined #yocto19:04
*** askdj31293 <askdj31293!c26e720a@> has joined #yocto19:09
*** ayoung <ayoung!~ayoung@2601:19c:4680:ee30::e734> has joined #yocto19:09
*** sno <sno!> has quit IRC19:13
*** B0ned1ger2 <B0ned1ger2!> has quit IRC19:18
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto19:22
*** kiwi_29 <kiwi_29!> has quit IRC19:42
smurrayRP: glibc 2.33 going in reminded me of this:
smurrayRP: it seems possible that aligning oe-core qemux86-64 / genericx86-64 to match x86-64-v2 might be worthwhile to match what other distros are doing19:49
*** kaspter <kaspter!~Instantbi@> has quit IRC19:55
*** kaspter <kaspter!~Instantbi@> has joined #yocto19:55
*** vmeson <vmeson!> has quit IRC19:58
khemyeah speculatively :)20:01
*** vmeson <vmeson!> has joined #yocto20:04
khemI think if we switch to using corei7 things will happen automatically but then we know that we are dumping core220:05
smurraykhem: yeah, raising the default seems like fun for the TSC to discuss20:08
smurraykhem: even w/o doing that, I could maybe see adding some tuning definitions to match v1/v2/v3 to make it easier for people that want it20:09
khemPerhaps defaulting to v2 is good option moving forward20:09
khemfolks who need v1 can test and let us know20:10
smurraythe other "fun" might be trying to enable getting multiple libraries in for the hwcaps stuff20:11
khemI think that only matters for binaries distros20:11
frayseems reasonable to have a way to do both.. pre "current gen" and origin20:11
smurraymight not be a large demand for that for OE users, yeah20:11
frayThe one thing likely needed is a way to tag which configs are v2 and v1..  I know I have atom systems I use (for home automation) that I have no idea what they count as20:12
smurraylots of digging around on, maybe ;)20:14
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC20:15
khemfray:  cat /proc/cpuinfo and we can find20:16
smurrayistr some test bits in the microarchitecture reference git repo, they might have a script20:16
khemif it has SSE4.2 then you are v2 most probably20:16
frayya, but who has access to every possible board.. like I said, I don't know what is a v2 and what isn't when it comes to the embedded stuff20:16
fraymodel name: Intel(R) Atom(TM) CPU D2700   @ 2.13GHz20:16
frayflags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl nonstop_tsc aperfmperf eagerfpu pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm arat20:17
frayI see sse2, but not '4.2'20:17
frayAdd to that all of the AMD, Cyrix and other stuff that is still in the market.. and both are probably needed..  I'm definitely not against adding v2 support, since it really is needed for current work20:18
*** kpo_ <kpo_!> has quit IRC20:36
*** kpo_ <kpo_!> has joined #yocto20:37
*** kiwi_29 <kiwi_29!> has joined #yocto20:59
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto20:59
*** kiwi_29 <kiwi_29!> has quit IRC21:02
*** minimaxwell <minimaxwell!> has quit IRC21:07
*** minimaxwell <minimaxwell!> has joined #yocto21:09
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC21:17
*** feddischson <feddischson!> has quit IRC21:23
*** kiwi_29 <kiwi_29!> has joined #yocto21:25
*** kiwi_29 <kiwi_29!> has quit IRC21:29
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto21:31
*** tgoodwin <tgoodwin!> has quit IRC21:37
*** eLmankku <eLmankku!> has quit IRC21:42
*** manuel_ <manuel_!> has joined #yocto21:42
*** eLmankku <eLmankku!> has joined #yocto21:42
*** JaBen <JaBen!~Thunderbi@2a02:8109:86c0:1c58:bd52:f0ef:80f0:e69e> has joined #yocto21:45
khemRP:  Found a solution for the x86 issue, you can try v2 of glibc plus the enable-cet patch21:57
RPkhem: will we see the pseudo build issue? i.e. do I need to figure that out first?21:57
RPkhem: I've merged binutils21:57
*** oberstet <oberstet!~oberstet@> has quit IRC21:58
RPsmurray: right, I just want to ensure that the support for older stuff still works. We can and should discuss the default21:59
*** ichabod_crane <ichabod_crane!~ichabod@> has joined #yocto22:18
ichabod_craneCan anyone direct me to a source for how to install a Python package in both python 2 and python 3? I've got a transient need to do both so I can port and test several packages to Python 3.22:21
*** zkrx <zkrx!> has quit IRC22:22
*** zyga_ <zyga_!~zyga@unaffiliated/zyga> has joined #yocto22:31
*** beneth <beneth!> has left #yocto22:35
*** vmeson <vmeson!> has quit IRC22:43
*** vmeson <vmeson!> has joined #yocto22:44
*** kpo_ <kpo_!> has quit IRC22:44
*** kpo_ <kpo_!> has joined #yocto22:44
khemRP: is the issue we are facing with glibc 2.33, I have cherry-picked the proposed patch locally and see if this helps out I will send this incremental patch after that22:45
khemRP:  yes pseudo for target will fail22:45
khemichabod_crane:  you need to include meta-python2 layer and then have python3-<module>.bb and python-<module>.bb recipes to build for each version of py22:46
*** camus <camus!~Instantbi@> has joined #yocto22:50
*** kaspter <kaspter!~Instantbi@> has quit IRC22:50
*** camus is now known as kaspter22:50
*** ichabod_crane <ichabod_crane!~ichabod@> has quit IRC22:52
RPkhem: I'll have a go at building pseudo locally, see if I can spot what we need there23:03
*** zkrx <zkrx!> has joined #yocto23:06
RPndec: we turned version going backwards off as we don't run prserv on the infra any more :(23:07
RPndec: the question with upgrades is always "compared to what", that is the hard bit23:07
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC23:11
*** goliath <goliath!> has quit IRC23:15
*** JaBen <JaBen!~Thunderbi@2a02:8109:86c0:1c58:bd52:f0ef:80f0:e69e> has quit IRC23:19
khemRP:  sounds good23:22
*** bobo__ <bobo__!> has quit IRC23:34
*** bobo <bobo!> has quit IRC23:34
*** sakoman <sakoman!~steve@> has quit IRC23:40
RPkhem: attempt at a fix in -next23:43
jonesv[m]I have this downstream kernel that builds up to `make[2]: *** No rule to make target 'msm8909-pm8916-mpp3-hw00.dts'.  Stop.` This dts is in the kernel sources in `arch/arm/boot/dts/qcom/`, and the name ("mpp3") corresponds to how the manufacturer calls the device. So it seemed correct.23:43
jonesv[m]The way I set it is in the machine file, with `KERNEL_DEVICETREE += "msm8909-pm8916-mpp3-hw00.dts"`. I have also read posts from 2016 that suggest using a `.dtb` (instead of `.dts`) and let the build system build it from the corresponding `.dts` by using `require recipes-kernel/linux/` in the kernel recipe. But does not seem to exist anymore with Gatesgarth.23:43
jonesv[m]Question: am I on the right track, or am I doing it completely wrong? 🙂23:43
*** minimaxwell <minimaxwell!> has quit IRC23:45
jonesv[m](note that the docs refers to ``, but I'm pretty sure I don't have it on gatesgarth 🤔:
*** minimaxwell <minimaxwell!> has joined #yocto23:47
RPkhem: did that cherry-picked patch work? Just wondering if I can start a build before sleeping! :)23:48
*** tgoodwin <tgoodwin!> has joined #yocto23:48
jonesv[m](also I `#inherit kernel`, which I read inherits kernel-devicetree, which is supposed to replace But somehow the way I specify `KERNEL_DEVICETREE += "msm8909-pm8916-mpp3-hw00.dts"` is not enough 😕23:48
*** sakoman <sakoman!~steve@> has joined #yocto23:56
khemRP:  seems to work let me send23:58

Generated by 2.17.2 by Marius Gedminas - find it at!