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"
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
Tokamak has joined #yocto
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #yocto
Tokamak has quit [Read error: Connection reset by peer]
perdmann has quit [Ping timeout: 244 seconds]
Tokamak has joined #yocto
perdmann has joined #yocto
tgamblin has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
camus has quit [Ping timeout: 272 seconds]
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
camus has joined #yocto
camus has quit [Quit: camus]
camus has joined #yocto
perdmann has quit [Ping timeout: 276 seconds]
perdmann has joined #yocto
perdmann has quit [Ping timeout: 240 seconds]
perdmann has joined #yocto
perdmann has quit [Ping timeout: 240 seconds]
perdmann has joined #yocto
perdmann has quit [Ping timeout: 240 seconds]
perdmann has joined #yocto
perdmann has quit [Ping timeout: 240 seconds]
perdmann has joined #yocto
amitk has joined #yocto
camus has quit [Remote host closed the connection]
camus has joined #yocto
sakoman has quit [Quit: Leaving.]
perdmann has quit [Ping timeout: 240 seconds]
perdmann has joined #yocto
alessioigor has joined #yocto
davidinux has quit [Read error: Connection reset by peer]
goliath has joined #yocto
alessioigor has quit [Quit: alessioigor]
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
perdmann has quit [Ping timeout: 276 seconds]
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
perdmann has joined #yocto
goliath has quit [Quit: SIGSEGV]
<LetoThe2nd> yo dudX
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
xmn has quit [Ping timeout: 272 seconds]
mckoan|away is now known as mckoan
<mckoan> good morning
davidinux has joined #yocto
Karsten[m]1 has joined #yocto
Schlumpf has joined #yocto
leon-anavi has joined #yocto
prabhakarlad has joined #yocto
mvlad has joined #yocto
alex88 has quit [Ping timeout: 260 seconds]
goliath has joined #yocto
gsalazar has joined #yocto
alex88 has joined #yocto
<fleg> Hi, I need to pass credentials to the build recipe as it downloads sources from servers that require authorization. I'm thinking about passing them as environment variables during build - is there a better option available?
<qschulz> o/
perdmann has quit [Ping timeout: 260 seconds]
perdmann has joined #yocto
alex88 has quit [Ping timeout: 268 seconds]
ptsneves has joined #yocto
<mckoan> fleg: use SSH keys
<fleg> mckoan: SSH keys won't really help me - I need bearer tokens to access a private npm registry
seninha has quit [Quit: Leaving]
alex88 has joined #yocto
Guest48 has joined #yocto
Perceval[m] has joined #yocto
<Guest48> Hi, I see "SPLASH_IMAGES:rpi =..." in one of the recipes from raspberry, this means the target is rpi correct? If so, how does yocto relate this target name to all the different machines such as 'raspberrypi2', 'raspberrypi3' etc.?
<LetoThe2nd> Guest48: bitbake-getvar -r core-image-minimal MACHINEOVERRIDES. its the SOC_FAMILY magic, i think.
<Guest48> LetoThe2nd Makes sense, thank you.
<amurray_tgp> fleg: I had this issue in the past, I think I first attempted to update the npm bbclass and standard fetchers to support credentials  - but ultimately threw it away and instead used: "bitbake nodejs-native -c devshell"
<amurray_tgp> before manually installing the NPM packages - and then tar'ing the node_modules directory into a tarball. It's not a nice way to do it, but worked for me. I can't find any details of how I updated the fetchers to support credentials sorry.
florian has joined #yocto
perdmann has quit [Ping timeout: 244 seconds]
perdmann has joined #yocto
seninha has joined #yocto
<fleg> amurray_tgp: I've updated fetchers already - added the "Authorization: Bearer" header to the wget fetcher - since the npmsw fetcher basically collects all the URIs and passes them to the wget fetcher. But yeah, I need to pass the token there somehow. The change is small, but I am talking with my employer about upstreaming it (or at least posting to
<fleg> the mailing list for the review, as I'm new to yocto and it probably isn't up to standards)
<fleg> right now I will get the environment variable with the target hostname in the variable name and a given prefix, and use its value as the token. It's simple and easy, but it's kind of going around everything else in yocto, so I'm asking if I'm missing something for that purpose
<qschulz> fleg: you will need to remove those two variables from the sstate-cache though otherwise your sstate-cache cannot be shared and a change of credentials will trigger a rebuild
ptsneves has quit [Ping timeout: 240 seconds]
<qschulz> fleg: vardepsexclude varflag to be used I think
ptsneves has joined #yocto
<amurray_tgp> fleg: I'm not an expert in this btw, most of my understanding came from this page - https://wiki.yoctoproject.org/wiki/TipsAndTricks/NPM - it'd be great if it could be updated to reflect the best way of handling private npm repos
mihai has joined #yocto
<fleg> amurray_tgp: my understanding is that private repos are currently simply not supported - as those bearer tokens are not implemented in any way in the wget fetcher, so I had to get creative here
jpuhlman_ has joined #yocto
jpuhlman is now known as Guest1266
jpuhlman_ is now known as jpuhlman
<fleg> qschulz: thanks a lot! Do you think in general this env approach is a good idea? Also: considering that those env variables will be per-hostname, should I somehow try to handle vardepsexclude on the python (fetcher) side, or should it be left to the user (the .conf files or recipes)?
<qschulz> fleg: is there really no system-wide/out-of-yocto solution for this kind of auth with wget?
Guest1266 has quit [Ping timeout: 255 seconds]
<qschulz> fleg: e.g. .netrc?
<fleg> qschulz: I am looking at netrc right now, but I don't see any mention of it supporting Authentication: Bearer header
<fleg> in general wget documentation says to look elsewhere for netrc documentation, and wherever I look doesn't seem to mention anything about anything else than a simple host-user-pass
<fleg> but I'm still looking - maybe I omitted something
<rburton> khem: wil fix up today
<qschulz> fleg: you can always send patches to gauge interest or get feedback
<qschulz> fleg: make sure you add Stefan Herbrechtsmeier in Cc, because I think they're the main person behind the work on npm
<fleg> qschulz: I'm planning do so once I get an okay from my employer. Also thanks for the contact, I'll add him
<fleg> also a quick glance at the wget's netrc parsing code hints that it only supports username and password authentication: https://git.savannah.gnu.org/cgit/wget.git/tree/src/netrc.c#n314
<qschulz> fleg: do the pythonic way, do not ask for permission but forgiveness :)
<qschulz> just send the patches :D
<fleg> qschulz: I was planning to do so, even if they wouldn't be merged at least the next person having the same issue would see the changes I did and decide for themselves if they want to patch their yocto with it or not ;)
<qschulz> fleg: I like people in that kind of mindset :) OSS FTW :)
Guest48 has quit [Ping timeout: 252 seconds]
perdmann has quit [Ping timeout: 276 seconds]
perdmann has joined #yocto
florian_kc 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
Guest48 has joined #yocto
perdmann has quit [Ping timeout: 260 seconds]
perdmann has joined #yocto
perdmann has quit [Ping timeout: 240 seconds]
perdmann has joined #yocto
<Guest48> What does 'outsuffix' mean and what does it do? Google tells me the word should be "out suffix" and searching it with the yocto keyword also didn't provide much useful info. It is written here: "file://psplash-raspberrypi-img.h;outsuffix=raspberrypi"
perdmann has quit [Ping timeout: 264 seconds]
perdmann has joined #yocto
<qschulz> Guest48: see function in the recipe
<qschulz> it's a psplash specific
<Guest48> qschulz Thank you!
vermaete has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
Guest39 has joined #yocto
Guest39 has quit [Client Quit]
nemik has quit [Ping timeout: 244 seconds]
gsalazar has quit [Remote host closed the connection]
vermaete has quit [Ping timeout: 252 seconds]
leon-anavi has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
gsalazar has joined #yocto
dvorkindmitry has joined #yocto
<rburton> sigh, i think buildpaths has revealed a bug in clang
perdmann has quit [Ping timeout: 272 seconds]
perdmann has joined #yocto
otavio has joined #yocto
<RP> rburton: oops :/
<RP> rburton: no good code change goes unpunished
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
<rburton> so buildpaths triggers a lot more with clang
<rburton> my hunch is that it's not doing the prefix map dance on relative paths
<rburton> ie libzstd is build using ../lib/foo.c
<rburton> [ 73b] /yocto/ross/build/tmp/work/armv8a-poky-linux/zstd/1.5.2-r0/git/lib
<rburton> and a build path appears in the debug symbols
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
frieder has joined #yocto
prabhakarlad has quit [Quit: Client closed]
frieder has quit [Remote host closed the connection]
<rburton> RP: polite request for picobuild 0.2 to be accelerated into oe-core as it fixes the known fallout in meta-oe
Tokamak has quit [Ping timeout: 255 seconds]
wkawka has joined #yocto
vermaete has joined #yocto
Tokamak has joined #yocto
<RP> rburton: done
<RP> rburton: not good with clang. Maybe it is doing the prefix mapping before resolving the path or something?
<rburton> yeah maybe
<rburton> guess i need to whittle it down to a minimal reproducer
pgowda_ has joined #yocto
paulg has joined #yocto
Tokamak has quit [Ping timeout: 244 seconds]
xmn has joined #yocto
Tokamak has joined #yocto
<wkawka> Hi, how can I check if my additional kernel config is added to image/
<qschulz> wkawka: mmm what is exactly the question? it is a bit confusing to me
<qschulz> usually you use a config at build time for the kernel, it does not need to be in image/
<qschulz> are you asking how to check if your config fragment/defconfig was taken into account for the kernel compilation?
<wkawka> I created additional kernel config (in which i want to enable leds) and this didn't work, but I want to chceck if it was taken or not
<wkawka> maybe I just missed something
<qschulz> wkawka: bitbake -c menuconfig virtual/kernel
<qschulz> and check in the explorer if your option was selected
<qschulz> (press the '/' key to enter search)
xmn has quit [Quit: ZZZzzz…]
<wkawka> This is what I was looking for
<wkawka> thanks
<Guest48> qschulz Other than for viewing purposes, can we/is it recommended to make changes to the kernel using "bitbake -c menuconfig virtual/kernel"? Or won't it have any effect?
<qschulz> Guest48: any modification made to the kernel config with menuconfig can be very easily lost
<Guest48> clear
<qschulz> when you clean your build directory, or something triggers a rebuild of the kernel (a dependency of the kernel has changed for example)
<qschulz> then your changes are lost
<qschulz> *however*, you should absolutely do modifications to the kernel defconfig with menuconfig, be it through bitbake or manually
<qschulz> it is very difficult to modify a defconfig by hand, to the point where it makes absolutely no sense to do it
<qschulz> once your modifications are done, go to your WORKDIR and you can see the new .config in the build directory of the kernel
<qschulz> you can have a defconfig too if you run savedefconfig
<qschulz> then up to you to decide how you want to share those changes, a full defconfig or a config fragment
<qschulz> see docs for how to share those changes
<Guest48> qschulz JPEW thanks, that clears it up
Tokamak has quit [Ping timeout: 255 seconds]
Tokamak has joined #yocto
jmiehe has joined #yocto
Tokamak has quit [Ping timeout: 244 seconds]
Tokamak_ has joined #yocto
leon-anavi has joined #yocto
<mckoan> Anyone noticed this on latest Dunfell? ERROR: zlib-intel-1.2.11.1.jtkv6.3-r0 do_patch: Applying patch 'CVE-2018-25032.patch' on target directory
* mckoan m-) branches mismatch, sorry
Guest48 has quit [Quit: Client closed]
kscherer has joined #yocto
perdmann has quit [Ping timeout: 260 seconds]
sakoman has joined #yocto
vermaete has quit [Ping timeout: 252 seconds]
perdmann has joined #yocto
tomzy_0 has joined #yocto
gsalazar has quit [Read error: Connection reset by peer]
gsalazar_ has joined #yocto
<tomzy_0> Hello, have any of you tried to prepare encrypted rootfs for imx using Yocto? I am wondering how that could be achieve. Some external script would be needed to create empty, encrypted partition and later write my generated rootfs into that?
prabhakarlad has joined #yocto
perdmann has quit [Ping timeout: 240 seconds]
perdmann has joined #yocto
<vin[m]> How can I make bitbake ignore the SSH keys during a git checkout?
perdmann has quit [Ping timeout: 244 seconds]
vermaete has joined #yocto
perdmann has joined #yocto
dacav has joined #yocto
manuel1985 has joined #yocto
paowz_ has quit [Ping timeout: 255 seconds]
Tokamak_ has quit [Ping timeout: 244 seconds]
<mckoan> tomzy_0: fs encryption is not managed directly by Yocto/bitbake, you have to create your scripts to create it on the host and to decrypt on the target. Most importantly manage the key that is the weak part of the chain.
manuel1985 has quit [Ping timeout: 276 seconds]
gsalazar_ has quit [Quit: Leaving]
gsalazar has joined #yocto
Tokamak has joined #yocto
<Xagen> what's the best way to find out which recipes in the image that i'm building lead to a particular dependency?
<Xagen> the one i'm trying to track down seems to be buried quite a ways (dependency of a dependency of a dependency)
vermaete has quit [Quit: Client closed]
<mckoan> Xagen: see bitbake -g and Generating Dependency Graphs
<tomzy_0> mckoan Ok, so because I need to format whole partition before encryption, I should do it on host and provide key to target in order to decrypt? What if I will have two copy of rootfs in my image. Could I use dmsetup in initramfs to encrypt partition using data from second copy?
vermaete has joined #yocto
amurray_tgp has quit [Quit: Client closed]
paowz_ has joined #yocto
dgriego has joined #yocto
amurray_tgp has joined #yocto
<qschulz> Xagen: delete the recipe and see what fails to build :)
vermaete has quit [Quit: Client closed]
<Xagen> qschulz: this is proving to be more helpful than the dependency graphs, although they give a lot of good information
leon-anavi has quit [Read error: Connection reset by peer]
leon-anavi has joined #yocto
goliath has quit [Quit: SIGSEGV]
<rburton> RP: i guess it would be quite bad for build times to make zstd depend on meson-native
<rburton> or is meson early in the build chain already...
<rburton> the zstd makefiles are 99% bonkers and we build zstd twice
florian_kc has quit [Ping timeout: 244 seconds]
<mckoan> tomzy_0: you could
Schlumpf has quit [Quit: Client closed]
<rburton> abelloni: can you drop the mesa patch from your next please (upstream rejected)
angman has joined #yocto
pgowda_ has quit [Quit: Connection closed for inactivity]
angman has quit [Client Quit]
<rburton> abelloni: and the two cve-check patches because they're both ugly
florian_kc has joined #yocto
<rburton> RP: see NAKs from me for next above
Tokamak has quit [Ping timeout: 244 seconds]
Tokamak has joined #yocto
ruslan has joined #yocto
amurray_tgp has quit [Quit: Client closed]
<ruslan> Can anyone point me how to add libsupc++ to yocto image? Do I need to write recipe myself? Oh maybe I missed it? I've tried to look into layer index, but haven't found it.
perdmann has quit [Ping timeout: 240 seconds]
leon-anavi has quit [Quit: Leaving]
Schlumpf has joined #yocto
<RP> rburton: NAKs for next? you mean mesa?
<RP> rburton: I haven't really looked at how messy the meson or zstd dependency trees are but we should be careful with them
perdmann has joined #yocto
wkawka has quit [Quit: Client closed]
<qschulz> couldn't find a recipe for it
jatedev has joined #yocto
<qschulz> but if it's a correctly written cmake-based project, the recipe should basically be: license info+src_uri+inherit cmake
gsalazar has quit [Read error: Connection reset by peer]
Schlumpf has quit [Quit: Client closed]
ptsneves has quit [Ping timeout: 240 seconds]
<ruslan> qschulz: I found, that libsupc++ is a part of libstdc++ and should be installed with gcc.
<jatedev> I would like to use the read-only feature of bitbake-hashserve with dunfell. What do you think about starting a separate instance based on newer code and having dunfell use it?
perdmann has quit [Ping timeout: 244 seconds]
perdmann has joined #yocto
<rburton> RP: mesa, cve-check, and now zlib :)
<rburton> is anyone else seeing sndfile1 fail with latest master?
tomzy_0 has quit [Quit: Client closed]
alimon has joined #yocto
florian has quit [Quit: Ex-Chat]
nemik has quit [Ping timeout: 240 seconds]
jatedev has quit [Quit: Client closed]
nemik has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
mckoan is now known as mckoan|away
seninha has quit [Quit: Leaving]
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
goliath has joined #yocto
jpuhlman_ has joined #yocto
jpuhlman has quit [Killed (molybdenum.libera.chat (Nickname regained by services))]
jpuhlman_ is now known as jpuhlman
prabhakarlad has quit [Quit: Client closed]
jatedev has joined #yocto
ruslan has quit [Quit: Client closed]
ruslan has joined #yocto
<RP> rburton: ok, thanks!
perdmann has quit [Ping timeout: 272 seconds]
perdmann has joined #yocto
denisoft81 has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
Tokamak has quit [Ping timeout: 255 seconds]
Tokamak has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
jatedev has quit [Quit: Client closed]
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
ruslan has quit [Quit: Client closed]
perdmann has quit [Ping timeout: 276 seconds]
perdmann has joined #yocto
Tokamak has quit [Ping timeout: 244 seconds]
Tokamak has joined #yocto
denisoft81 has quit [Quit: Leaving]
amitk has quit [Ping timeout: 264 seconds]
prabhakarlad has joined #yocto
Tokamak has quit [Ping timeout: 244 seconds]
Tokamak has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
manuel1985 has joined #yocto
zeddii has quit [Ping timeout: 264 seconds]
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
berndlaser[m] has joined #yocto
Tokamak has quit [Ping timeout: 255 seconds]
Tokamak has joined #yocto
<hushmoney> what does clm1 stand for as in clm1.bbclass?
<hushmoney> s/clm1/cml1/g
perdmann has quit [Ping timeout: 264 seconds]
zeddii has joined #yocto
perdmann has joined #yocto
fitzsim has quit [Ping timeout: 276 seconds]
<JaMa> hushmoney: interesting question, the bbclass was introduced very long time ago (already included in 2004 https://git.openembedded.org/openembedded/commit/?h=master&id=a780643c4b6aa11e1a36965a69df7116477c7b4c) and it was very small until https://git.openembedded.org/openembedded/commit/?h=master&id=f6433e75a047a2d38ab60efea8a7ab7cc3dcd822 Don't know what it really stands for
<hushmoney> yes that's what i saw too
fitzsim has joined #yocto
<hushmoney> i grepped the linux source for cml1 and only found references to some clock in modules and device trees, don't think that's related
<hushmoney> wow, good find! still doesn't answer what cml stands for, but at least i know now to what it refers and that more answers lie outside of yocto history
<hushmoney> here it is. cml = Configuration Menu Language
<hushmoney> JaMa: thanks!
<hushmoney> sort of an odd choice for that bbclass name, but at least now i know where it came from
seninha has joined #yocto
<kergoth> hushmoney: it's named based on the ocnifguration language it interacts with, as it's common to more than just kernels, it's used by busybox, buildroot, and other projects as well
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
dacav has quit [Quit: leaving]
manuel1985 has quit [Ping timeout: 272 seconds]
perdmann has quit [Ping timeout: 272 seconds]
perdmann has joined #yocto
Tokamak has quit [Ping timeout: 244 seconds]
nemik has quit [Ping timeout: 276 seconds]
Tokamak has joined #yocto
nemik has joined #yocto
xenador77 has joined #yocto
Tokamak_ has joined #yocto
Tokamak has quit [Ping timeout: 255 seconds]
kscherer has quit [Quit: Konversation terminated!]
denisoft81 has joined #yocto
florian_kc has joined #yocto
perdmann has quit [Ping timeout: 240 seconds]
perdmann has joined #yocto
perdmann has quit [Ping timeout: 272 seconds]
perdmann has joined #yocto
tgamblin has quit [Quit: Leaving]
nemik has quit [Ping timeout: 272 seconds]
denisoft81 has quit [Quit: Leaving]
nemik has joined #yocto
tgamblin has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
perdmann has quit [Ping timeout: 276 seconds]
perdmann has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
seninha has quit [Read error: Connection reset by peer]
mvlad has quit [Remote host closed the connection]
seninha has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
perdmann has quit [Ping timeout: 276 seconds]
perdmann has joined #yocto
perdmann has quit [Ping timeout: 272 seconds]
perdmann has joined #yocto
Tokamak_ has quit [Ping timeout: 244 seconds]
Tokamak has joined #yocto
dtometzki has quit [Ping timeout: 240 seconds]
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
Tokamak has quit [Read error: Connection reset by peer]
dtometzki has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto