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"
xantoz has quit [Ping timeout: 240 seconds]
olani_ has quit [Ping timeout: 276 seconds]
olani- has quit [Ping timeout: 276 seconds]
olani has quit [Ping timeout: 276 seconds]
RP has quit [Ping timeout: 240 seconds]
RP has joined #yocto
qschulz has quit [Remote host closed the connection]
qschulz has joined #yocto
xantoz has joined #yocto
camus has quit [Quit: camus]
xmn has joined #yocto
zenodub has quit [Quit: WeeChat 3.5]
kscherer has quit [Quit: Konversation terminated!]
camus has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
seninha has quit [Quit: Leaving]
sakoman has quit [Quit: Leaving.]
sakoman has joined #yocto
olani has joined #yocto
olani- has joined #yocto
olani_ has joined #yocto
jclsn has quit [Ping timeout: 240 seconds]
jclsn has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
Guest42 has joined #yocto
<Guest42> hello! I am new to Yocto and I would like some help setting up a real-time preempt_rt kernel for beaglebone black through Yocto.
<Guest42> I have attempted a variety of things but so far nothing has been working
<Guest42> If possible, could someone give me a step by step tutorial to accomplish this?
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
schtobia has quit [Quit: Bye!]
nemik has joined #yocto
schtobia has joined #yocto
schtobia has quit [Client Quit]
schtobia has joined #yocto
camus1 has joined #yocto
camus has quit [Ping timeout: 250 seconds]
camus1 is now known as camus
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
<Guest42> can anyone help me here? or should I try to send an email to the mailing list?
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
alessioigor has joined #yocto
olani_ has quit [Ping timeout: 272 seconds]
olani has quit [Ping timeout: 240 seconds]
olani- has quit [Ping timeout: 272 seconds]
amitk has joined #yocto
sakoman has quit [Quit: Leaving.]
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<ykrons> Hello
<Guest42> Hello
Guest42 has quit [Quit: Client closed]
xmn has quit [Ping timeout: 240 seconds]
<ykrons> How should the runtime dependencies be specified in multilib world? For example, if I build lib32-mypackage in a 64bit image and it depends for build on libcurl, I will add DEPENDS += "curl" and it will add lib32-curl to sysroot, that's fine.
ptsneves has joined #yocto
<ykrons> But for runtime dependencies, if mypackage depends on curl, if I add RDEPENDS_{PN} += "curl", I think that it will add lib32-curl to my image whereas the dependency can be resolved by the 64bit curl package. So should runtime dependencies be specified out of the recipe ?
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
chep has quit [Ping timeout: 264 seconds]
mthenault has joined #yocto
frieder has joined #yocto
zpfvo has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
<xcm> hello. i added dnsmasq to my image and now it fails with "ERROR: QA Issue: /usr/bin/dnsmasq-resolvconf-helper contained in package dnsmasq requires /bin/bash, but no providers found in RDEPENDS:dnsmasq? [file-rdeps]". i don't seem to even need this file because it says it's inteded for systemd-only anyway. what can i do?
<xcm> fwiw my build does (not on purpose) pull bash in
<xcm> ah, `RDEPENDS:${PN} += "bash"` in the .bbappend fixed it.
arielmrmx has quit [Ping timeout: 240 seconds]
Payam has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
zpfvo has quit [Quit: Leaving.]
zpfvo has joined #yocto
leon-anavi has joined #yocto
mckoan|away is now known as mckoan
amitk has quit [Quit: leaving]
Algotech has joined #yocto
Algotech has quit [Quit: Leaving]
Algotech has joined #yocto
florian has joined #yocto
JaMa has quit [Quit: reboot]
JaMa has joined #yocto
JaMa has quit [Quit: reboot]
JaMa has joined #yocto
Bardon_ has quit [Ping timeout: 268 seconds]
Algotech75 has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
alessioigor has quit [Quit: alessioigor]
nemik has joined #yocto
alessioigor has joined #yocto
camus has quit [Ping timeout: 240 seconds]
camus has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
Algotech has quit [Quit: Leaving]
Algotech has joined #yocto
DarkKnight has joined #yocto
Bardon has joined #yocto
mvlad has joined #yocto
<DarkKnight> Hi everyone. I add CFLAGS_my_module.o := -DDEBUG to the makefile of an out of tree kernel module. But somehow bitbake does not apply additional cflags. What am I doing wrong?
<rburton> the makefile is probably overriding it with the variables used
<rburton> not really a yocto thing, that's just how make works
<DarkKnight> rburton Thanks! that makes sense. Is there any way that I can force it in recipe to include the additional flag?
mckoan is now known as mckoan|away
Algotech has quit [Quit: Leaving]
Algotech75 is now known as Algotech
seninha has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
DarkKnight has quit [Quit: Client closed]
Tyaku has joined #yocto
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
goliath has joined #yocto
Daedaluz has joined #yocto
Guest36 has joined #yocto
Guest36 has quit [Client Quit]
ptsneves has quit [Ping timeout: 276 seconds]
GNUmoon has quit [Ping timeout: 258 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
ptsneves has joined #yocto
Ram-Z has quit [Ping timeout: 272 seconds]
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
ptsneves has quit [Ping timeout: 260 seconds]
ptsneves has joined #yocto
mthenault has quit [Ping timeout: 276 seconds]
ptsneves has quit [Remote host closed the connection]
ptsneves has joined #yocto
Ram-Z has joined #yocto
GNUmoon has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
xmn has joined #yocto
seninha has quit [Remote host closed the connection]
ptsneves has quit [Ping timeout: 250 seconds]
seninha has joined #yocto
ptsneves has joined #yocto
Tyaku has quit [Ping timeout: 240 seconds]
zpfvo has quit [Ping timeout: 252 seconds]
<wyre> how is BB_NUMBER_THREADS and PARALLEL_MAKE determined when they aren't set in conf/local.conf?
<mcfrisk> wyre: thread count of the build machine is checked. note that amount of RAM is not and building non-trivial can result in oom killer breaking the build.
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
mthenault has joined #yocto
<JaMa> mcfrisk: not only the build, but it will also sometimes kill your networking and you might fail to ssh after OOMK runs (happened to me few times - always only when I'm traveling and need to access home builder only remotely)
zpfvo has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
<mcfrisk> JaMa: ouch, that's bad. I've only seen compiler related processes getting killed when doing bitbake builds in the last 8 years. I've been very lucky it seems.
<mcfrisk> or my CPU thread count relation to availabe RAM has been "good". Less than rwo Gb of RAM
<mcfrisk> less than two Gb of RAM per thread would have been really bad, but I've been over that
florian_kc has joined #yocto
<JaMa> mcfrisk: http://dpaste.com/E822JE7HZ few unlucky kills in last few months
<JaMa> I should figure out how to configure OOMK to always kill some cc1plus first
<JaMa> and more recent days, similar story https://dpaste.com/7G3ZMQAWW
<JaMa> with 128G ram on 32c/64t threadripper
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
<mcfrisk> I used a 128G and 42 thread machine for a long time, 64 seems to be too much. Are BB_PRESSURE_MAX_CPU and BB_PRESSURE_MAX_MEMORY ready to replace thread counts already?
<JaMa> mcfrisk: I've set BB_PRESSURE_* some time ago and it helps a bit, but doesn't prevent OOMK when I get crazy and trigger 2nd build in parallel (usually thinking that I have valid sstate for all the big recipes and just needing to refresh the image a bit - and ending rebuilding chromium or something anyway)
<JaMa> or when I impatient and trigger 2nd build after 1st _almost_ finished building chromium - in this case BB_PRESSURE makes it a bit worse, because chromium build in 1st build slows down significantly and instead of finishing before 2nd one starts it ends with both builds crawling at the same time
chep has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
sakoman has joined #yocto
ptsneves has quit [Ping timeout: 240 seconds]
<fray> I ran into an issue. Updating from Honister to Langdale. I am using 'crda' for wifi stuff, but something changed and now packagegroup-base-wifi requires wireless-regdb-static (all from poky/oe-core), but this has a conflicts with crda
<fray> is crda no longer used? Or is there some other way to tell the system to NOT use packagegroup-base-wifi, but use crda instead?
Daedaluz has quit [Quit: Connection closed]
amitk has joined #yocto
<fray> I don't know
<fray> If it's no longer needed that is fine, just the descriptions of the contents don't make that obvious.. the commit you pointed to seems to make it that its no longer needed
<JaMa> I've removed it from our images a while ago https://github.com/webosose/meta-webosose/commit/927418fe527d945bee5ff441d5adcc73b96ff640 in dunfell already
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
<fray> thanks, it does seem like it's obsolete. I've removed it locally as well
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
<LetoThe2nd> ... did I mention the YPS 2022.11 cfp lately? https://summit.yoctoproject.org/yocto-project-summit-2022-11/cfp
vladest has quit [Remote host closed the connection]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
kscherer has joined #yocto
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.11) Nov 29-Dec 1, 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"
vladest has joined #yocto
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
vladest has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
vladest has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
Payam has quit [Quit: Client closed]
nemik has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
goliath has quit [Quit: SIGSEGV]
mthenault has quit [Ping timeout: 250 seconds]
vladest has quit [Remote host closed the connection]
florian_kc has quit [Ping timeout: 250 seconds]
kmaincent[m] has quit [Quit: You have been kicked for being idle]
hmw[m] has quit [Quit: You have been kicked for being idle]
florian has quit [Quit: Ex-Chat]
nemik has quit [Ping timeout: 250 seconds]
vladest has joined #yocto
nemik has joined #yocto
vladest1 has joined #yocto
vladest has quit [Ping timeout: 252 seconds]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
vladest1 has quit [Ping timeout: 252 seconds]
frieder has quit [Remote host closed the connection]
<vvn> many systemd services explode with using read-only-rootfs. Is one supposed to edit all such services to set a different state directory or disable writes if possible or am I missing a (systemd) feature?
PhoenixMage has quit [Ping timeout: 252 seconds]
PhoenixMage has joined #yocto
PhoenixMage has quit [Ping timeout: 250 seconds]
<Ebeneezer_Smooge> vvn, it depends on the service. most of the ones I know of explode when /var is read-only which is pretty much meant to be a 'no-no'. using an overlay os is the usual solution
PhoenixMage has joined #yocto
<Ebeneezer_Smooge> at least in Fedora... which I thought I was answering in versus yocto.
leon-anavi has quit [Quit: Leaving]
alessioigor has quit [Quit: alessioigor]
<vvn> Ebeneezer_Smooge: what annoys me with an overlayfs for / is that it requires a custom initrd script to do so if I'm not mistaken
<Ebeneezer_Smooge> yeah sorry I haven't done much of this outside of seeing what is 'read-write' on an ostree system
PhoenixMage has quit [Ping timeout: 272 seconds]
PhoenixMage has joined #yocto
florian_kc has joined #yocto
zpfvo has quit [Remote host closed the connection]
<mischief> we use a readonly /, but the details of how we got there are forgotten now :-)
<kergoth> Overlay or bind mounts for specific paths, there are options
Tokamak has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
xcm has quit [Read error: Connection reset by peer]
xcm_ has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
Estrella has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
Estrella has joined #yocto
arielmrmx has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
Minvera has joined #yocto
manuel_ has joined #yocto
<mischief> in our system we just never write to /, and only have rw mounts for /var and some other stuff
amitk has quit [Quit: leaving]
<vvn> that's where I'm heading too
<vvn> overlay for /etc and /var or eventually the whole / if I can make it "pure-system" (i.e. fstab entries only and no custom scripts in the initrd)
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
GillesM has joined #yocto
manuel_ has quit [Ping timeout: 260 seconds]
<mischief> we have ro /etc to.. and moved most interesting stuff into /var or /run
<khem> with systemd you will need /etc writable too for best results
nemik has quit [Ping timeout: 250 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
GillesM has quit [Remote host closed the connection]
GillesM has joined #yocto
GillesMM has joined #yocto
GillesM has quit [Read error: Connection reset by peer]
manuel_ has joined #yocto
mvlad has quit [Remote host closed the connection]
Minvera has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
Guest2996 has joined #yocto
<Salamandar> Even without systemd, ro /etc prevents setting the hostname, ip address network config, etc
olani has joined #yocto
olani- has joined #yocto
olani_ has joined #yocto
manuel_ has quit [Ping timeout: 240 seconds]
<mischief> hm, we don't seem to have those sorts of problems with ro /etc. it has been possible for years, at least with tricks, to use systemd with ro / and /etc
<Salamandar> So how does hostnamectl work on ro /etc ?
<Salamandar> also networkmanager stores its config in /etc, although i would not be surprised if you can change that ^^
kscherer has quit [Quit: Konversation terminated!]
Guest2996 has quit [Quit: Client closed]
<mischief> we don't use hostnamectl, nor networkmanager
goliath has joined #yocto
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
prabhakarlad has quit [Quit: Client closed]
<moto-timo> yocti, make me a sandwich
<yocti> moto-timo: Error: "make" is not a valid command.
<paulg> yocti, tell moto-timo to go make his own damn sammich.
<yocti> paulg: The operation succeeded.
<moto-timo> yocti, tell paulg the sammich was delish
<yocti> moto-timo: The operation succeeded.
<paulg> Fun with bots!
<paulg> Apparently they don't have spell check either.
<paulg> we'll have to get halstead on that.
<halstead> paulg: what needs to be changed?
<paulg> halstead, we are just joking around on how yocti didn't complain about me typing "sammich"
<halstead> Ah.. no spell check indeed
florian_kc has quit [Ping timeout: 240 seconds]