ndec changed the topic of #yocto to: "Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Join us or Speak at Yocto Project Summit (2022.05) May 17 - 19, more: https://yoctoproject.org/summit | Join the community: https://www.yoctoproject.org/community | IRC logs available at https://www.yoctoproject.org/irc/ | Having difficulty on the list or with someone on the list, contact YP community mgr ndec"
xmn has joined #yocto
adams[1]13 has joined #yocto
dev1990 has quit [Quit: Konversation terminated!]
jmiehe has quit [Quit: jmiehe]
sakoman has quit [Quit: Leaving.]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
adams[1]13 has quit [Quit: Client closed]
adams[1] has quit [Quit: Client closed]
adams[1] has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
sakoman has joined #yocto
amitk has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
ardo has quit [Quit: ZNC 1.8.2 - https://znc.in]
ardo has joined #yocto
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
adams[1] has quit [Quit: Client closed]
manuel1985 has joined #yocto
otavio_ has quit [*.net *.split]
dacav has quit [*.net *.split]
Chaser has quit [*.net *.split]
mckoan|away has quit [*.net *.split]
JPEW has quit [*.net *.split]
reatmon has quit [*.net *.split]
KanjiMonster has quit [*.net *.split]
rfs613 has quit [*.net *.split]
smooge has quit [*.net *.split]
neverpanic has quit [*.net *.split]
mckoan|away has joined #yocto
otavio_ has joined #yocto
dacav has joined #yocto
Chaser has joined #yocto
JPEW has joined #yocto
reatmon has joined #yocto
KanjiMonster has joined #yocto
smooge has joined #yocto
rfs613 has joined #yocto
neverpanic has joined #yocto
rob_w has joined #yocto
frieder has joined #yocto
manuel1985 has quit [Ping timeout: 276 seconds]
goliath has quit [Quit: SIGSEGV]
goliath has joined #yocto
leon-anavi has joined #yocto
Guest5 has joined #yocto
xmn has quit [Ping timeout: 244 seconds]
mckoan|away is now known as mckoan
sakoman has quit [Quit: Leaving.]
mvlad has joined #yocto
dev1990 has joined #yocto
Schlumpf has joined #yocto
Schlumpf has quit [Client Quit]
Mahdi14 has joined #yocto
Mahdi14 has quit [Quit: Client closed]
DarkKnight has joined #yocto
manuel1985 has joined #yocto
<DarkKnight> Hi, how can I add javac to the SDK generated by yocto?
<LetoThe2nd> DarkKnight: should be by using meta-java and adding it to TOOLCHAIN_HOST_TASK, presuming that it is supported.
Schlumpf has joined #yocto
ptsneves has joined #yocto
LetoThe2nd has quit [Quit: WeeChat 3.5]
LetoThe2nd has joined #yocto
dev1990 has quit [Quit: Konversation terminated!]
Notgnoshi has quit [Ping timeout: 240 seconds]
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
florian has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
Notgnoshi has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
rfried has joined #yocto
mborges has quit [Quit: You have been kicked for being idle]
<ptsneves> good morning all
ptsneves has quit [Quit: ptsneves]
ptsneves has joined #yocto
<qschulz> o/
<RP> ptsneves: https://git.yoctoproject.org/poky/commit/?h=master-next&id=1276baaae9523170917004bf1ebdb7ef6fd47738 is what I think we should do (roughly) but sadly it breaks things
<ptsneves> Oh. What got broken? Can i help?
<ptsneves> I was trying to get the poky test passing by removing the cleanall but i have a dirty workspace and other things got in the way. When i have time today i will try to finish fixing the test.
<RP> ptsneves: there are a few fixes in master-next but the big worry is that testsdkext is failing on eSDKs
<RP> ptsneves: I ran out of time last night so I'm trying to reproduce this morning
<ptsneves> do you have the builderbot logs or was it locally?
<RP> ptsneves: I still don't have that test that got broken working right either
<ptsneves> @RP Thanks
<ptsneves> @RP Is this the issue on the eSDK: "do_deploy_source_date_epoch_setscene: No sstate archive obtainable, will run full task instead."
<RP> ptsneves: there is something broken with sstate fetching, yes
<ptsneves> @RP ok. Not so bad then. We kind of established that the DL_DIR code was related to state cache.
DarkKnight has quit [Quit: Client closed]
<RP> ptsneves: right
kami has joined #yocto
Schlumpf has quit [Quit: Client closed]
ardo has quit [Quit: ZNC 1.8.2 - https://znc.in]
ardo has joined #yocto
wkawka has joined #yocto
<ptsneves> @RP sent the fix to the openembedded's test_invalid_recipe_src_uri. It is one more line than what you have in the master-next. I tested it is sucessfull
<qschulz> ptsneves: missing SoB :)
<ptsneves> @qschulz argh..:( thanks for the catch
<ptsneves> maybe we could add this hook https://stackoverflow.com/a/46536244/227990 and then it would be added by default?
<RP> ptsneves: would you be interested/able to tweak it a little bit more? I'd like to get the "The paths that were searched were:" in this message
florian_kc has joined #yocto
<ptsneves> @RP sure. I need to add the signoff either way
<RP> ptsneves: that is a local thing, we can't add that for you
<LetoThe2nd> ptsneves: that would implicitly assume that everybody who sends a patch is authorized to, instead of requiring people to explicitly acknowledge it.
Guest5 has quit [Quit: Client closed]
kami has quit [Quit: Client closed]
<ptsneves> LetoThe2nd: indeed, but if a user sends something by sharing he is already doing a deliberate action of sharing. Regardless it is not technically feasible. I had the wrong impression that client side hooks were trackeable by git
<LetoThe2nd> ptsneves: the difference is between "sharing information" and "being authorized to convey this information to some other project"
<rburton> I can email out a confidential document but that doesn't mean I was authorised to :)
Habbie has quit [Ping timeout: 244 seconds]
<RP> ptsneves: it seems we use DL_DIR in there for file:// to file:// url mappings in MIRRORS
<ptsneves> @RP cant we add DL_DIR to the FILESPATH where those mappings are expected, localizing that logic to the state cache?
<ptsneves> even if the end result does not end up being very different from the current one.
<RP> ptsneves: it is in FILESPATH :/
<RP> ptsneves: I don't understand where the issue is as yet, just that it is the file:// to file:// mirror code
Guest5 has joined #yocto
<ptsneves> Unable to get checksum for man-db SRC_URI entry 404: file could not be found
<ptsneves> RP: Will try to have a look later. In the mean time i corrected the oeqa patch to point to the correct mailinglist(oe-devel) instead of bitbake-devel and added the signedoff. For the bitbake patches i added the paths searched to the errors and also fixed a missing signoff. The bbfatal looks something like:
<ptsneves> The following paths were searched:
<ptsneves> /tmp/bitbake-fetch-ngoygvt7/localsrc/404
<ptsneves> /tmp/bitbake-fetch-ngoygvt7/download/404
<RP> ptsneves: great, that makes it as useful as the current fetch failure now
<RP> ptsneves: thanks, I'll continue to try and see if I can work out what is going wrong with sstate
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
Habbie has joined #yocto
wkawka has quit [Quit: Client closed]
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
wkawka has joined #yocto
<wkawka> Hi, how can I trace wic blupgin? I have created a new plugin from the old one, but my created grub.cnf file is being overwritten, and I can't find anything what is doing that
<wkawka> plugin*
<RP> ptsneves: I think this is actually a missing mkdir :/
<ptsneves> @RP can you point to the code you are looking at?
<RP> ptsneves: https://git.yoctoproject.org/poky-contrib/commit/?h=rpurdie/t222&id=4883e1ab76842ec84d931960027e537ed3aac0f7
<ptsneves> ah there was a funny assumption there
<ptsneves> localpath used to point to the last entry of localpaths which was DL_DIR
<ptsneves> or better it is DL_DIR in current code.
<RP> ptsneves: I think it was just luck it usually worked. This might not fix all the issues, not sure yet. Will need another run. It certainly makes the logs quieter
<ptsneves> I think the DL_DIR fallback was providing a very pervasive fallback even in cases where it was not meant to.
rob_w has quit [Remote host closed the connection]
<LetoThe2nd> I have a Makefile-based package that with INIT_MANAGER = "systemd" borks out on ld not understanding -Wl,-O1 whereas on "sysvinit" it builds, and I totally can't find why. Can't find a difference in the LDFLAGS and TARGET_LDFLAGS. any pointers?
kscherer has joined #yocto
<rburton> LetoThe2nd: have you compared the log.do_compiles with and without systemd?
pabigot has quit [Remote host closed the connection]
<RP> or even the configure logs
sakoman has joined #yocto
alicef has quit [Quit: install gentoo]
alicef has joined #yocto
alicef has quit [Client Quit]
<LetoThe2nd> heh, tried to do that now (thanks rburton), so did a cleansstate and tried to reproduce. guess what happens? recipe builds for systemd.
alicef has joined #yocto
pabigot has joined #yocto
<rburton> bare makefile recipes are notoriously bad. it might be rebuilds which break it
<rburton> if you can, implement a working 'make clean'
alicef has quit [Quit: install gentoo]
alicef has joined #yocto
<qschulz> or just delete the recipe tmpdir between tries also?
<rburton> that's cheating if the goal is to solve the problem
<LetoThe2nd> who cares about solving....
<qschulz> rburton: it was the way to get the log.do_compile/do_configure back?
<qschulz> I assume the WORKDIR was dirty and make didn't re-run completely
<qschulz> and if LetoThe2nd is using the same workdir for his tries with INIT_MANAGER, it might mess up the attempts?
<qschulz> much knowledgeable, very expert
* LetoThe2nd much depressed, very drink
<wkawka> During booting my system hangs on systemd-journald[1843]: Received client request to flush runtime journal.
<wkawka> It is hanging for abiut 90 seconds, then i can run shell for maintenance
<rburton> LetoThe2nd: if this is something you wrote, just use a proper build tool. if its something else, shout at the author to use a proper build tool
<LetoThe2nd> rburton: i will save my breath instead of shouting at some chinese author writing boot0 for allwinner, tbh.
<qschulz> rburton: I think we just closed the loop :) what you said is the first thing LetoThe2nd always say when someone asks something about makefile based projets :D
<wkawka> i don't know what to do about it, when i type `ls / -laht` i don't se any 1000 PID, all of them are root
<LetoThe2nd> qschulz: yeah, you're totally right. the problem is those usually are... not exactly cooperating.
<qschulz> LetoThe2nd: line 5 already shows there's little experience with Yocto :/
<LetoThe2nd> qschulz: lol yeah.
<qschulz> and LIC_FILES_CHKSUM
<qschulz> oh my
<LetoThe2nd> qschulz: have to say though that the original author is (was) really junior, so no blaming from my end.
<qschulz> shouldn't have passed review though :/
<LetoThe2nd> qschulz: blame khem
<qschulz> LetoThe2nd: there are a few newer commits in the git repo, I doubt it'll make a difference but why not try :)
<qschulz> (one teaches junior, not blame them BTW :) )
<RP> smurray, dl9pf: Looks like meta-agl has a reproducibility issue in connman-ncurses: https://autobuilder.yoctoproject.org/typhoon/#/builders/120/builds/1408/steps/14/logs/warnings
<dl9pf> ok
<dl9pf> in the debug symbols ... hmmm
<RP> dl9pf: we're down to that, a kernel issue and something with mulltilibs messing up
<dl9pf> ok either me or scott will look
adams[1] has joined #yocto
mckoan has quit [Quit: Quitting irssi IRC Client, bye.]
xmn has joined #yocto
mckoan has joined #yocto
<agherzan> RP: I worked today on a CI issue we had where ninja was killing our build nodes and I've backport + implemented this https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/merge_requests/196
<agherzan> 1. it backports a patch so ninja will adhere to the cgroup limits
<agherzan> 2. it implements a way for injecting a load average configuration via an environment variable (this can be set in the CI infra and/or we can discuss a sane default for oe-core)
<agherzan> We use 2 for recipes doing bare ninja stuff, for gn-based recipes but ideally it would be used in cmake too (to pass the relevant argument down to ninja). Do these look sane for pushing to master/kirkstone.
<agherzan> ?
elroy has joined #yocto
<elroy> Hi. I find a lot of text in the Yocto manual about running GDB on the target. Are there any tips for using GDB on the host to analyze postmortem core dumps sent back by users?
<JaMa> agherzan: looks nice (I would be definitely interested to test this), but doesn't "export MAXLOAD_NINJA" screw with sstate reuse?
<ptsneves> JaMa: Would this not be good for the patches on bitbake for the cpu pressure?
<agherzan> Yes, it would and it will. I'll need to fix that JaMa
<JaMa> agherzan: if you happen to add it in bitbake.conf's BB_HASHEXCLUDE_COMMON then please remove PARALLEL_MAKE from BB_HASHCONFIG_IGNORE_VARS as it's listed in both variables (and the later includes BB_HASHEXCLUDE_COMMON so it's listed twice)
<agherzan> Yup
<agherzan> That's what I had in mind
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
denisoft81 has joined #yocto
<denisoft81> hi guys, I received this error message when I boot up my system.... https://pastebin.com/m8bUUqzk
<denisoft81> kindly, how can I do?
<denisoft81> I'm trying to boot the system using SD card
<RP> agherzan: you should let vmeson have a look at that!
<landgraf> RP: Summary with reproducer https://bugzilla.yoctoproject.org/show_bug.cgi?id=14858#c3 . Note: this happens during do_rootfs when dnf installs packages
<RP> agherzan: I like the idea from the description but I'm a bit out of time right now to look in detail
<rburton> denisoft81: tried a different SD card?
<denisoft81> hi rburton, I only have this card in this moment
<RP> landgraf: thanks. I see it is the fact the ptest pulls in openssh itself which causes the issues :(
<RP> landgraf: I don't know how we'd solve this :(
<landgraf> RP: The only idea I have is to build openssh-sftp-server in different recipe but it's not nice "workaround" :-/
<JaMa> landgraf: why not BAD_RECOMMENDATION we discussed before? works for me
<landgraf> khem:
<landgraf> whoops. Sorry. fat fingers
<landgraf> JaMa: because it will block openssh even if it's needed
<agherzan> RP: thanks. Given the good feedback I'll just start working on an oe-core series and we can iterate there.
<RP> JaMa: that would break the ptest package :/
<JaMa> it would block only openssh-sftp-server recomendation, right? not a dependency on openssh
<landgraf> JaMa: as a workaround we use 'PACKAGE_EXCLUDE_COMPLEMENTARY = openssh'
<RP> agherzan: vmeson has done work in this area so has a specialist interest
<agherzan> Sure. I'll keep him in the loop
<RP> JaMa: I see what you mean, that would mean the scp is broken though?
<vmeson> RP: agherzan: -- reading -- cgroups eh? no root perms needed even to set things up?
<JaMa> RP: yes, you have to use -O for scp to work
<JaMa> RP: I've seen your message about -O being only temporary, but I haven't found any confirmation from upstream about it
<landgraf> JaMa: with 'PACKAGE_EXCLUDE_COMPLEMENTARY openssh-sftp-server will be installed so you can use scp still.
<agherzan> vmeson: that is only used to use the existing cgroup limits. It doesn't set them
<agherzan> That is only to use*
<agherzan> It basically sets the -j based on the cgroup limit.
<vmeson> agherzan: cool. That would certainly help. Instead of load average, we've found that /proc/pressure/cpu regulation using either avg10 or a manual 1 second diff of the total pressure is more responsive.
<landgraf> so I've found this less invasive than bad_recommendation. the only disadvantage is missed openssh-ptest/-dev/-dbg package on openssh-based images with *-pkgs but this can be simply worked around with IMAGE_INSTALL:append = "openssh-<pkg>"
<vmeson> agherzan: I'm in another meeting so I'll skim now and read more carefully later.
<agherzan> vmeson: but this will throttle ninja directly as it spawns new jobs
<agherzan> How are you using the CPU pressure?
adams[1] has quit [Ping timeout: 252 seconds]
<agherzan> Oh I see, you are only saying that this will be a better metric
<vmeson> agherzan: so far only to limit bitbake from starting new tasks but I think the same approach would be useful for ninja/make. Let me find the link....
<vmeson> agherzan: yes.
<agherzan> We would need to implement it in make/ninja etc
<agherzan> The limit on bitbake will be just the tip of the iceberg because we need the throttling for the invoked builds too
<vmeson> agherzan: https://lists.openembedded.org/g/bitbake-devel/message/13797 <--- uses avg10 - that helps but it's a bit too slow.
<agherzan> I see.
<vmeson> agherzan: agree. I can share some of the work we've done so far if you like. Setting PARALLEL_MAKE to a small value of say 1/Number-of-builds does help limit the overload of a full buld but won't help with chromium for example.
<agherzan> I would start for now with the existing support in make and ninja and we can improve it with PSI afterwards
<vmeson> along with the /proc/pressure regulation that is.
<agherzan> Chromium was cmake?
<agherzan> If yes, I plan to extend the ave load conf to cmake too
<vmeson> agherzan: sure, it'll help. I did test using ninja -l with chromium and as you'd expect the number of compilation jobs shot above and below the targetted limit but it did help on average.
manuel1985 has quit [Ping timeout: 244 seconds]
* vmeson shifts focus back to the meeting he's in...
<agherzan> We'll run some tests on our farm. And tell you how it goes
<agherzan> Cheers. Thanks
dmoseley_ has quit [Ping timeout: 244 seconds]
Bardon has joined #yocto
<vmeson> agherzan: chromium build with ninja -l 60 or so: https://photos.app.goo.gl/8fzKwWHAEgrd7m3S8
Bardon_ has quit [Ping timeout: 244 seconds]
<agherzan> vmeson: interesting. I was expecting something like this too
<agherzan> That actually looks very good
<agherzan> Oh well. It's not 60 it's 50. But it's still decent.
<vmeson> agherzan: Yes 50. it's a good start a square wave is the goal . ;-)
<agherzan> Yes.
<vmeson> agherzan: close up: https://photos.app.goo.gl/V1ujJmbaS5oWbiCk8
dmoseley has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
manuel1985 has joined #yocto
nemik has joined #yocto
<agherzan> Makes sense. I think that is a good starting point
<agherzan> I'll also measure stuff on our side but based on your graphs it looks decent
<vmeson> agherzan: would the addition of cgroup make things even better?
<agherzan> It will limit the CPU upper bound of ninja
mckoan is now known as mckoan|away
nemik has quit [Ping timeout: 272 seconds]
<agherzan> So if you have a docker container, it will respect the limits set there
nemik has joined #yocto
<agherzan> (Docker as an example)
<vmeson> agherzan: I see. I haven't played with looking at cpu regulation in containers yet so I look forward to seeing your results.
frieder has quit [Remote host closed the connection]
vladest has joined #yocto
<agherzan> We use gitlab CI with docker runners and this makes the ninja processes respect the limits on the runners.
manuel1985 has quit [Ping timeout: 240 seconds]
AkkermT_ has quit [Ping timeout: 272 seconds]
fenrig has joined #yocto
<fenrig> Hi, how can I disable the memory tagging feature from my machine config? https://git.openembedded.org/openembedded-core-contrib/tree/meta/recipes-core/glibc/glibc_2.35.bb#n87
<fenrig> PACKAGECONFIG:remove = "memory-tagging" ?
<fenrig> is there a way to do it only for aarch64?
<JaMa> PACKAGECONFIG:remove:aarch64
<fenrig> can I do it from wherever?
<fenrig> this structure?
<qschulz> fenrig: in a bbappend for the recipe
<fenrig> I only have it when combining glibc2.35 with <linux5.4 on aarch64
<fenrig> so I would like to try to disable the feature only there :/
florian_kc has quit [Ping timeout: 240 seconds]
AkkermT_ has joined #yocto
<qschulz> fenrig: I don't think there's a guaranteed way to know which version of the kernel will be built from within recipes
<fenrig> too bad, I put a comment around it. As Im mainly focussing on linux containers which will be running on 4.14 or greater :/
nerdboy has quit [Ping timeout: 244 seconds]
<fenrig> qschulz: btw isnt the linux-libc-headers component an implicit dependency of all the packages that are to be built for the target? as its part of the toolchain
<JaMa> we work around this by specifying the kernel version to build in MACHINE.conf and then it can be used in other recipes, but that's not without its own issues as well
<fenrig> btw I dont have any kernel built, but I do need the headers in the cross compile toolchain to match the host
<fenrig> to clarify, the host of the container
jpuhlman_ has joined #yocto
jpuhlman has quit [Killed (zirconium.libera.chat (Nickname regained by services))]
jpuhlman_ is now known as jpuhlman
florian has quit [Quit: Ex-Chat]
<qschulz> JaMa: PREFERRED_VERSION isn't enforced I'm pretty sure?
nerdboy has joined #yocto
nerdboy has joined #yocto
nerdboy has quit [Changing host]
<JaMa> qschulz: correct PREFERRED_VERSION isn't
<JaMa> WEBOS_VERSION_KERNEL is and that's what our kernel recipe uses to define PV and SRCREV
fitzsim has joined #yocto
v0n has joined #yocto
xmn has quit [Ping timeout: 264 seconds]
Guest5 has quit [Quit: Client closed]
AkkermT_ has quit [Ping timeout: 264 seconds]
florian_kc has joined #yocto
alimon has quit [Read error: Connection reset by peer]
jpuhlman has quit [Remote host closed the connection]
jpuhlman has joined #yocto
leon-anavi has quit [Quit: Leaving]
alimon has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
tgamblin has quit [Ping timeout: 255 seconds]
denisoft81 has quit [Quit: Leaving]
ptsneves has quit [Ping timeout: 240 seconds]
manuel1985 has joined #yocto
wkawka has quit [Quit: Client closed]
janvermaete[m] has joined #yocto
<janvermaete[m]> Hi, I think setuptools-scm isn't needed anymore in the python3-jsonschema recipe.
AkkermT_ has joined #yocto
<janvermaete[m]> What to do? Email to mailinglist. A patch? But how to verify if the recipe is still working. I'm not using the recipe itself.
florian_kc has joined #yocto
amitk has quit [Ping timeout: 244 seconds]
<zeddii> RP: I have -stable updates, and then the next set of buildpaths fixes. They'd all go on top of my last ones (gen-mach-types). Want me to do a pull request, versus sending the 6 patches as singles .. that way the ordering is clear
<Xagen> i have an odd issue that i'm hoping someone can help solve
<Xagen> i have a binary that's failing to run due to it saying that it doesn't exist (but does)
<Xagen> and it looks like one of the libraries is the cause
<Xagen> when i use ldd on it from devshell, i see "/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found"
<rfried> Hi. I'm trying to add customized kernel (git) to a new BSP I'm creating.
<rfried> The build fails with: ERROR: Nothing RPROVIDES '${@oe.utils.conditional('KERNEL_IMAGETYPE',' (but /work/ramon/bsp/bsp/yocto/layers/meta-neureality/recipes-kernel/linux/linux-nr_5.18.bb RDEPENDS on or otherwise requires it)
<rfried> a complete error and recipe for kernel is here: https://www.toptal.com/developers/hastebin/zicogizivu.coffeescript
<rfried> I'm on Yocto Kirkstone.
<Xagen> but glibc 2.35 is what should be getting installed based on the recipes i see
<kanavin_> back in berlin! but not starting to work until 25th july or so
<Xagen> i think it's looking at my host glibc for some reason
<Xagen> not sure how to get around this
<rfried> Would love if someone can point me to what am I missing. because KERNEL_IMAGETYPE is defined in the machine config.
adams[1] has joined #yocto
<JPEW> rsalveti: After talking with RP, we (well, mostly RP) found a much simpler solution to the SPDX document problem we were seeing
manuel1985 has quit [Ping timeout: 272 seconds]
<JPEW> I just pushed the patch to the ML
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<JPEW> RP: it could also be `if isSPDXtask(task) and isSPDXtask(deptaskname)` so that it only applies to do_create_(runtime_)spdx -> do_create_(runtime_)spdx`. I can't decide if that's better
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
<jonmason> probably a stupid question, but any idea why pulseaudio would need m4-native with a binary toolchain but not native gcc?
manuel1985 has joined #yocto
<jonmason> doing an armv7 build of sato and seeing this (building sato for the first time for this platform, so unsure if this is a regression or not)
manuel1985 has quit [Ping timeout: 260 seconds]
manuel1985 has joined #yocto
<rsalveti> JPEW: awesome, let me take a look
manuel1985 has quit [Ping timeout: 240 seconds]
<rsalveti> ah, cool, changing sstatesig
manuel1985 has joined #yocto
<dmoseley> At the meeting in Nuremburg for EW, there was some discussion of using Matrix with IRC integration for accessing these channels. Does anyone have any links or docs on how to do this? Also, what would be the benefit of that setup over an IRC bouncer like ZNC? cc: LetoThe2nd
<JPEW> (very bottom)
<dmoseley> Any thoughts on the benefits?
<JPEW> dmoseley: Not from me
<JPEW> I use IRC Cloud FWWIW
manuel1985 has quit [Ping timeout: 244 seconds]
kscherer has quit [Quit: Konversation terminated!]
mvlad has quit [Remote host closed the connection]
AkkermT_ has quit [Ping timeout: 255 seconds]
AkkermT_ has joined #yocto
manuel1985 has joined #yocto
manuel1985 has quit [Remote host closed the connection]
manuel1985 has joined #yocto
<RP> JPEW: being specific may be beneficial
<RP> zeddii: thanks! I'll work it out :)
florian_kc has quit [Ping timeout: 244 seconds]
<JPEW> RP: ya I was leaning that will. Will send a v2
<RP> zeddii: seeing version sanity check failures :( https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3916 - did I get the patches wrong? :/
<zeddii> RP: I was rushing a bit. let me double check everything.
manuel1985 has quit [Ping timeout: 244 seconds]
olani has joined #yocto
<RP> zeddii: it might be the yocto-bsp versions looking at the pattern
<zeddii> RP: I didn't run my --release process on the last BSP bumps. that automatically bumps the version
<zeddii> I can send one with the version bumps. doing that now. (seeing if my script will work without SRCREVs changing at the same time)
<zeddii> it works. doing 5.10 and will send the patches.
<RP> zeddii: thanks!
* RP reruns the build and heads to sleep
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
olani has quit [Ping timeout: 272 seconds]